mcp-registry/io.github.api-jarvisclaw/jarvisclaw · v1.0.0
As of 2026-10-23 03:08 UTC, the Api Jarvisclaw Jarvisclaw MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 42 outages in 90 days, with a median recovery of 2 minutes.
320 AI models + 2,720 pay-per-call APIs. x402 USDC on Base or Solana, no API key.
Claude Code
claude mcp add --transport http api-jarvisclaw-jarvisclaw-mcp-server https://api.jarvisclaw.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"api-jarvisclaw-jarvisclaw-mcp-server": {
"type": "http",
"url": "https://api.jarvisclaw.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
9 of 9 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.api-jarvisclaw%2Fjarvisclaw/fixes
{
"name": "aip_estimate_cost",
"description": "Preview what a task will cost before committing — get an estimated price for an intent without running it or spending anything. Ideal for budget planning and comparing options up front. Free.",
"inputSchema": {
"type": "object",
"required": [
"intent"
],
"properties": {
"intent": {
"enum": [
"chat_completion",
"image_generation",
"video_generation",
"text_to_speech",
"web_search",
"knowledge_search"
],
"type": "string",
"description": "The intent type"
},
"optimize_for": {
"enum": [
"cost",
"quality",
"latency"
],
"type": "string",
"default": "cost"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "aip_execute_with_budget",
"description": "Run an AI task end-to-end with a hard spending cap you set. This is the primary AIP action: it resolves the best provider, runs a risk check, pre-deducts against your budget, executes the call, and settles on-chain via x402 — all in one step. You never overspend past max_total_usd, and settlement is automatic. Supports chat, image, video, speech, prompt optimization, web search, and knowledge search intents.",
"inputSchema": {
"type": "object",
"required": [
"intent",
"payload"
],
"properties": {
"intent": {
"enum": [
"chat_completion",
"image_generation",
"video_generation",
"text_to_speech",
"prompt_optimization",
"web_search",
"knowledge_search"
],
"type": "string",
"description": "The intent type"
},
"payload": {
"type": "object",
"description": "The actual request payload (e.g. {model, messages} for chat, {prompt, size} for images)"
},
"max_total_usd": {
"type": "number",
"default": 1,
"description": "Maximum budget for this request in USD (hard cap)"
},
"preferred_payment": {
"enum": [
"balance",
"credit",
"crypto",
"auto"
],
"type": "string",
"default": "auto",
"description": "Payment method preference"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "aip_list_intents",
"description": "Browse every AI task type AIP can route — chat, image, video, speech, web search, knowledge search — with a short description of each. Call this first to see what's on the menu before you resolve or execute. Free.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.api-jarvisclaw/jarvisclaw"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.api-jarvisclaw/jarvisclaw"}) over MCP.
aip_resolve ~373 tokensaip_execute_with_budget ~312 tokenschat ~265 tokenssearch_apis ~182 tokensdiscover_agents ~171 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.api-jarvisclaw%2Fjarvisclaw?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.api-jarvisclaw%2Fjarvisclaw?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.api-jarvisclaw%2Fjarvisclaw.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.api-jarvisclaw%2Fjarvisclaw.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.api-jarvisclaw%2Fjarvisclaw?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d964caf14eb779fb…, first seen 2026-10-17, included at leaf 1033 of 49,655. Version history · verify what your client received.
Compare: most reliable other servers · most reliable ml servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 03:08 UTC, the Api Jarvisclaw Jarvisclaw MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 42 outages in 90 days, with a median recovery of 2 minutes.
Api Jarvisclaw Jarvisclaw MCP server advertises 9 tools, including aip_estimate_cost, aip_execute_with_budget, aip_list_intents, aip_resolve, chat.
Point your MCP client at this streamable-http endpoint: https://api.jarvisclaw.ai/mcp
Glimind scanned all 9 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.