Break down the claim
Split the claim into checkable parts before gathering evidence.
Morassel breaks the claim down and gathers evidence in an Arabic workspace. The model does not declare the truth on its own, and no card is published before a named human reviewer approves it.
The reviewer decides
There are no delete tools, and the audit log does not store content.
A clear workflow from the claim to an approved card.
Split the claim into checkable parts before gathering evidence.
Record evidence and its sources as reviewable metadata.
The card is published only with a named reviewer's approval.
Use the service URL and your key.
Paste the claim or the link to check.
The human reviewer decides before anything is published.
Streamable HTTPhttps://morassel-mcp.marsaplatform.com/mcpBearer YOUR_API_KEYEvery request needs Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY.
https://morassel-mcp.marsaplatform.com/mcpclaude mcp add --transport http morassel https://morassel-mcp.marsaplatform.com/mcp \
--header "Authorization: Bearer YOUR_API_KEY"~/.cursor/mcp.json{
"mcpServers": {
"morassel": {
"url": "https://morassel-mcp.marsaplatform.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
}
}
}
}.vscode/mcp.json{
"servers": {
"morassel": {
"type": "http",
"url": "https://morassel-mcp.marsaplatform.com/mcp",
"headers": {
"Authorization": "Bearer ${input:morassel-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "morassel-key",
"description": "\u0627\u0644\u0645\u0631\u0627\u0633\u0644 API key",
"password": true
}
]
}VS Code asks for the key once and stores it securely.
claude_desktop_config.json{
"mcpServers": {
"morassel": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://morassel-mcp.marsaplatform.com/mcp",
"--header",
"Authorization:${AUTH_HEADER}"
],
"env": {
"AUTH_HEADER": "Bearer YOUR_API_KEY"
}
}
}
}Claude Desktop reaches remote servers through mcp-remote, which needs Node.js. Restart the app after editing.
curl -s -X POST https://morassel-mcp.marsaplatform.com/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1"}}}'With a valid key you get the initialize result. Without a key you get 401.
The original page states: “13 MCP tools”. The full list is generated from tools/list once a read key is configured for this site; until then any MCP client shows it after you connect.
No. It helps organise; the decision belongs to a human reviewer.
The audit log does not store content or reviewer notes.
There are no delete tools in the current version.
The real response for a request without a key:
WWW-Authenticate: Bearer realm="morassel"
{"error":"unauthorized","message":"Missing bearer token - send Authorization: Bearer <key> or X-API-Key"}Send the header exactly as Authorization: Bearer YOUR_API_KEY or X-API-Key: YOUR_API_KEY.