IBAMA Autuações
warningsapi.mcp.ai
Looks up IBAMA environmental fines for a person or company from the CPF or CNPJ. Platform-hosted, no
https://api.mcp.ai/p_ibama_autuacoesOAuthMCP 2025-11-25v0.9.339last checked 3 Sep 2026spoke MCP on 3 of 3 checks (30 days)initialize in 765 msWill my client connect?
Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.
✓Claude CodeConnects
The authorization server advertises RFC 7591 registration, so Claude Code can register itself and sign you in through the browser.
claude mcp add --transport http ibama-autua-es https://api.mcp.ai/p_ibama_autuacoesClaude Code docs · read on 2026-08-30
✓Claude (claude.ai & Desktop)Connects
The authorization server advertises RFC 7591 registration, so Claude (claude.ai & Desktop) can register itself and sign you in through the browser.
Settings → Connectors → Add custom connector, then paste https://api.mcp.ai/p_ibama_autuacoes.
Claude (claude.ai & Desktop) docs · read on 2026-08-30
✓ChatGPTConnects
The authorization server advertises RFC 7591 registration, so ChatGPT can register itself and sign you in through the browser.
Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://api.mcp.ai/p_ibama_autuacoes.
ChatGPT docs · read on 2026-08-30
✓CursorConnects
The authorization server advertises RFC 7591 registration, so Cursor can register itself and sign you in through the browser.
{
"mcpServers": {
"ibama-autua-es": {
"url": "https://api.mcp.ai/p_ibama_autuacoes"
}
}
}Cursor docs · read on 2026-08-30
✓VS Code (Copilot)Connects
The authorization server advertises RFC 7591 registration, so VS Code (Copilot) can register itself and sign you in through the browser.
{
"servers": {
"ibama-autua-es": {
"type": "http",
"url": "https://api.mcp.ai/p_ibama_autuacoes"
}
}
}VS Code (Copilot) docs · read on 2026-08-30
How to authenticate
Checked against the endpoint by our probe on 3 Sep 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://api.mcp.ai |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓S256 |
| Grant types | authorization_code, refresh_token |
| Scopes | mcp:read, mcp:execute, integrations:read |
| Protected-resource metadata | ✕Not found Without it a client has to guess where the authorization server lives. |
| Anonymous access | Handshake succeeds; 7 tools listable |
| Credentials demanded in prose | ✕marketplace These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
What the probe found
1 of the 7 tools listed anonymously say in their own descriptions that they need an account or a key (marketplace), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
The server exposes a public surface before authorization: ibama_autuacoes_consultar, show_version, report_bug, connect, toolkit_info, marketplace, authenticate.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Own this server?
Sign in to claim this listing by proving control of its host.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/ibama-autua-es)