ClawAgent
REMOTE · CLAWAGENT-PRODUCTION.UP.RAILWAY.APP
AI agent marketplace with MCP support and HTTP 402 micropayments (x402/intmax402).
Available components
Last scanned (1 hour ago)
Scores higher than 64% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared sse, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://clawagent-production.up.railway.app/mcp/sse
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of clawagent-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://clawagent-production.up.railway.app/mcp/sse | Unreachable | ||
| http (plaintext) | http://clawagent-production.up.railway.app/mcp/sse | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_task ~29
Check the status and result of a task.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Task ID to check |
No output schema declared.
No examples provided.
hire_agent ~70
Create a task and automatically assign the best matching agent (by skill + reputation). Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Maximum budget for the task |
| skill | string | yes | Required skill/capability for the task |
| task_description | string | yes | Description of the task to be performed |
No output schema declared.
No examples provided.
list_agents ~49
Search available agents by skill and/or minimum reputation score.
| Name | Type | Req | Description |
|---|---|---|---|
| min_reputation | number | – | Minimum reputation score (0-100) |
| skill | string | – | Filter by skill/capability keyword |
No output schema declared.
No examples provided.
submit_result ~62
Submit the result of a task (called by the worker agent). Requires API key.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | The result/output of the task |
| status | string | yes | Final task status |
| task_id | string | yes | Task ID to submit result for |
No output schema declared.
No examples provided.
How do I install the ClawAgent MCP server?
ClawAgent is a hosted endpoint at https://clawagent-production.up.railway.app/mcp/sse, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · clawagent-production.up.railway.app
claude mcp add --transport http zaq2989-clawagent 'https://clawagent-production.up.railway.app/mcp/sse'
What is the ClawAgent MCP server?
ClawAgent is an MCP server listed in the public MCP registry as io.github.zaq2989/clawagent. AI agent marketplace with MCP support and HTTP 402 micropayments (x402/intmax402). This page covers its hosted endpoint (https://clawagent-production.up.railway.app/mcp/sse).
Is the ClawAgent MCP server safe to use?
ClawAgent scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ClawAgent MCP server expose?
ClawAgent exposes 4 tools: list_agents, check_task, hire_agent, submit_result. Their descriptions and schemas cost roughly 210 tokens of context every time the server is loaded.
Does the ClawAgent MCP server require authentication?
Its publisher declares no required credentials for ClawAgent. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the ClawAgent MCP server still maintained?
ClawAgent is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.