io.github.afrotools/afrotools · v1.0.0 · communication
afro.tools is healthy: it completed an MCP handshake in 1264 ms and exposes 5 tools.
Open-source API specs for African providers (payments, SMS, KYC, delivery) for AI agents.
Endpoint: https://mcp.afro.tools/mcp (streamable-http)
Repository · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 1264 ms |
| Last checked (UTC) | 2026-10-31T19:30:28.373Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-31T19:30:28.373Z | Healthy | 1264 |
list_providers | Lists all providers and their verification status. Every listed provider is AI Ready: its specs give you a structured description to integrate it from. They can still contain errors — that is what each capability's "status" reports. all_verified is true only when ALL its capabilities have status "ve |
search_specs | Searches specs by words and filters by category, channel, provider, country, currency, status or capability type. Returns the matching providers, each with its countries, currencies, sandbox flag, docs URL and the matching capabilities (name, type, status, example_prompt) — no endpoints, schemas, go |
get_spec | Returns the full spec payload for a provider + capability, including canonical_example.ts source code. Use this to get the complete integration guide — auth pattern, endpoint, schemas, gotchas, and a TypeScript example — before writing API calls. The response includes a "status" field: - "verifie |
request_spec | Logs a request for a spec that doesn't exist yet and notifies maintainers. Call this when a user asks for a provider or capability that has no spec in the registry (check list_providers first). This helps maintainers prioritize which specs to write next. Args: - provider (string): Provider slug e |
report_integration | Builds a pre-filled GitHub link to report how an integration went against a spec — it worked, or the spec is wrong. Call it when the user confirms an integration works against the real API (sandbox or production), or when you find the spec does not match the API. Reports are how specs get verified a |