NAIF Gravity — MCP & Integration Diagnostics

NAIF Gravity provides bounded diagnostics and repair workflows for MCP, AI-agent integrations, APIs, authentication, and webhooks, with reproducible developer-facing diagnostics and machine-readable agent discovery.

Start with the Diagnostic Hub or visit NAIF Gravity.

This repository contains public diagnostic guidance, a small Python MCP health-check script, issue templates, and discovery metadata. It is not a complete source distribution of the hosted service.

Service discovery

These hosted pages map common developer problems to a focused diagnostic or repair path:

Problem or intent	Start here
API integration failures, request/response mismatch, or small integration fixes	API integration diagnostic
JSON validity, malformed payloads, or schema-adjacent checks	JSON validity check
Automation workflow failures and broken task handoffs	Automation factory
Data transformation, structured output, or pipeline repair	Data factory
Docker service health, container startup, or deployment checks	Docker health fix
Small bounded repair verification	Repair check

The canonical home page is naifgravity.com. These direct service links make the relationship between each developer problem and its destination explicit for both people and search engines.

Try the MCP health check

Requires Python 3 and uses only the standard library. Run against a server you own or are authorized to test:

bash

git clone https://github.com/naief9961-tech/ai-growth-engine.git
cd ai-growth-engine
python3 tools/mcp_health_check.py https://your-mcp.example/mcp

Replace the example URL with your endpoint. The script negotiates initialize, sends notifications/initialized, and reads tools/list when advertised. It supports JSON and SSE responses, optional bearer authentication through an environment variable, and bounded pagination; it never calls a tool. Protocol errors produce a nonzero exit status without printing server response bodies or secrets.

See the quick start and limitations before interpreting the result. This is a discovery probe for supported handshake-era revisions, not a full MCP conformance suite.

Try the offline webhook signature example to see why parsing and reserializing JSON can break raw-body verification. It uses synthetic data and makes no network requests.

Find the right diagnostic path

Failure	Useful evidence	Start here
MCP connection, session, or schema	Transport, client/server versions, sanitized JSON-RPC error	MCP diagnostic template
API authorization or OAuth	HTTP status, auth scheme, expected behavior, sanitized error code	API/Auth diagnostic template
Webhook delivery or processing	Provider, delivery and handler status, signature result, redacted payload shape	Webhook diagnostic template

Read the troubleshooting index for common 401, 403, invalid_grant, raw-body signature, retry, and idempotency failures. Open an issue using the matching template once you have a minimal reproduction.

GitHub issues are public. Remove tokens, cookies, signing secrets, private keys, payment credentials, and customer data before sharing evidence.

For AI-agent builders

Agent discovery documentation describes the hosted MCP transport, A2A Agent Card, and canonical domain. server.json contains the provider's MCP registry metadata.

Documentation and discovery metadata describe the provider's interfaces; they do not guarantee current availability or certify protocol conformance. Diagnostic discovery does not automatically execute a production repair.

Contribute

Useful contributions include reproducible sanitized examples, clearer troubleshooting steps, and corrections to diagnostic documentation. Explain the problem, expected behavior, and how to reproduce or verify your change. Never include private production logs.

This repository also contains material from the earlier AI Growth Engine project. See the historical README and the existing contribution guide for that context. Historical bounty amounts, payout automation, and endpoint status are not current commitments.

If these diagnostics help you debug an integration, consider starring the repository so other builders can find it.

Service boundary

The hosted service is available at https://naifgravity.com. Public GitHub diagnostic guidance and optional commercial repair workflows are separate; an issue or contribution does not purchase a service or guarantee a repair.