Remote MCP · Endpoint

CNPJ MCP server

No. CNPJ answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_cnpj

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/cnpj-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
42 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Free Brazilian CNPJ lookup (legal name, status, partners) + lawsuit discovery. Public data, no login
Listing
From the official MCP registry (active).
Recent checks of CNPJ
CheckedResultHandshake
1 hour agoHandshake completed42 ms
2 days agoHandshake completed214 ms
4 days agoHandshake completed36 ms
5 days agoHandshake completed32 ms
7 days agoHandshake completed96 ms
8 days agoHandshake completed238 ms
9 days agoHandshake completed51 ms
12 days agoHandshake completed155 ms
14 days agoHandshake completed111 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed86 ms
18 days agoHandshake completed45 ms
19 days agoHandshake completed361 ms
20 days agoHandshake completed53 ms
20 days agoHandshake completed63 ms
21 days agoHandshake completed28 ms
23 days agoHandshake completed36 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CNPJ and makes no claim about it beyond what these checks measured.