_ registry / mcp + a2a MCP · checked 2h ago

pydantic.dev

https://pydantic.dev

Registry code: 264961923dc6c57d

api record
endpoint
https://logfire-us.pydantic.dev/mcp
door code
dd2a5ce66629bc8f
protocol
MCP ·0.3
authentication
bearer
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pydantic.dev live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is pydantic.dev free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does pydantic.dev have?
6 tools: Manage dashboards, Manage feature flags, Manage notification channels, Query telemetry data, Execute Python in a sandbox, Manage alerts.
Is pydantic.dev safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.5%· all time 99.2%

latency
151ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1038 checks · signed record
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 auth-required 6 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • manage-dashboards auth-required never probed

    Create, read, update, and delete Logfire dashboards and their panels, variables, and layout groups using Perses-compatible JSON.

    observabilitydashboardslogfire

  • manage-feature-flags auth-required never probed

    Create and update managed variables (feature flags), version snapshots, rollouts, targeting overrides, and labels.

    feature-flagsrolloutslogfire

  • manage-notification-channels auth-required never probed

    Create and update Slack, Discord, Opsgenie, and webhook notification channels for alerts.

    notificationslogfire

  • query-telemetry auth-required never probed

    Run SQL SELECT queries against a Logfire project's traces, logs, metrics, and exceptions for investigation and exploration.

    observabilitytelemetrysqllogfire

  • exec-python-sandbox auth-required never probed

    Run Python code in a secure sandbox with access to Logfire platform helper functions for advanced analysis.

    pythonsandboxlogfire

  • manage-alerts auth-required never probed

    Configure SQL-based alerts that periodically run and notify channels when results match. Inspect alert history and current firing state.

    alertsmonitoringlogfire

_ try it over a2a through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 264961923dc6c57d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/264961923dc6c57d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/264961923dc6c57d/badge.svg)](https://brick.blue/agent/264961923dc6c57d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
20%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on pydantic.dev 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.