NAIF Gravity — MCP Diagnostics & Recovery

What NAIF Gravity — MCP Diagnostics & Recovery does

NAIF Gravity provides structured investigation for failures involving MCP servers, AI-agent integrations, APIs, webhooks, JSON-RPC requests, configuration, and authentication. The main diagnostic entry point accepts one sanitized failure and returns bounded evidence, likely causes, and suggested next steps. It does not modify the caller's system or create a commercial transaction during diagnosis.

The repository is not a complete source distribution of the hosted service. It includes public diagnostic guidance, issue templates, discovery metadata, and a small Python MCP health-check script. A separate local Node.js skill, NAIF JSON Rescue, can validate a sanitized JSON sample before an external call.

How it works

Connect an MCP client to the hosted Streamable HTTP endpoint at https://naifgravity.com/mcp and negotiate through MCP. A normal browser request is not the intended discovery method and may receive HTTP 405. The service can also be discovered through its A2A Agent Card, AI catalog, agent catalog API, and official MCP Registry listing.

Start with diagnose_issue. It produces bounded diagnostic evidence and may include a suggested repair service. Diagnostic calls may record limited operational attribution or telemetry, but they do not alter the caller's system, create a quote, initiate checkout, charge a payment method, or start repair work.

For a normal paid repair flow, call quote_repair only after diagnosis and when a priced repair is wanted. Pass the returned quote identifier to prepare_repair after explicitly selecting that quote and one of its offered payment rails. This creates checkout instructions but does not send funds or start execution. After the required buyer action, call verify_repair with the checkout identifier and, where required, the payer's transaction hash.

Tools and capabilities

• diagnose_issue investigates one sanitized MCP, API, webhook, agent, or integration failure.
• quote_repair creates a non-binding quote for a selected or automatically matched public service.
• prepare_repair accepts an existing quote and prepares checkout on one offered rail.
• request_delegated_purchase handles a separately authorized autonomous purchase under an explicit spending cap. It creates its own quote and checkout for one of four supported micro-services.
• verify_repair confirms payment for a checkout created by prepare_repair and may return the related job.

The payment paths include Apple Pay, Base USDC, and TRON USDT where eligibility and authorization permit. Apple Pay can require human approval; wallet flows return transfer instructions rather than sending funds. Payment verification reports confirmed, already-confirmed, or unsuccessful states without fabricating success.

Setup and configuration

For the hosted MCP service, configure a compatible client with the Streamable HTTP URL. The repository's local JSON checker requires Node.js 18 or newer and can be run after cloning the repository. The checker validates syntax locally without uploading data, changing files, or spending funds. Its sample input and hosted diagnostic inputs should be sanitized and bounded; hosted Micro Tool V2 samples are limited to 4,096 UTF-8 bytes.

Limitations and notes

Do not submit secrets, private keys, payment credentials, raw customer records, or other sensitive data. Repeating quote or delegated-purchase calls can create new quote or checkout records because those operations are intentionally non-idempotent. prepare_repair is for an existing quote; it is not the autonomous purchasing route. The service does not itself send payments, charge buyers, verify arbitrary transactions, or directly begin repair execution.