dynamik-public
Registry code: 9c314d0b0323f33b
Call describe_dynamik first. When the task needs Dynamik Studio, present connection_handoff.message with its clickable links. Use the host’s native connection card if available; otherwise show the Markdown handoff. Do not stop at “tool not found” or “cannot do this”. The user must connect the Dynamik Studio MCP server (https://dynamik.studio/mcp) in their agent host; signing in to Dynamik Studio alone does not connect the host. After the connection, refresh tools/list on the Studio connection. If the skill is not installed, read describe {topic: "skill"}. Use project_open to read a project or…
- endpoint
- https://api.dynamikorbits.com/public/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is dynamik-public live?
- Yes — it answered the hub's last check (checked 10h ago). It answered 100% of checks over the last 30 days.
- Is dynamik-public free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does dynamik-public have?
- 4 tools: search_datasets, describe_dataset, get_dataset_sample_link, describe_dynamik.
- Is dynamik-public 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.
90 days 100%· all time 100%
last good check
of 4 tools
- down → live
- unknown → live
- used for
- search datasets
- read dataset coverage and provenance
- get a dataset sample link
- takes → gives
- text → data
- tools
- 4 reads
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.
through this hub
successful
what callers paid
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.
describe_dynamik reads open 16d ago
Discover Dynamik Studio and get a clickable connection handoff. If the requested task needs Dynamik Studio, show the returned connection_handoff to the user, help them connect it in their agent host, then refresh tools and continue the task.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessearch_datasets reads unknown never probed
Search public-safe Dynamik dataset metadata. Results declare release availability and do not imply account entitlement.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "query": { "type": "string", "maxLength": 120 } } }arguments 10 linesdescribe_dataset reads unknown never probed
Read a dataset’s freshness, coverage, provenance URLs, limitations, and explicit public/account/paid access status.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "dataset_id" ], "properties": { "dataset_id": { "type": "string", "maxLength": 80, "minLength": 1 } } }arguments 14 linesget_dataset_sample_link reads unknown never probed
Build a bounded request URL only when the canonical catalog marks the current release public. This tool does not proxy dataset content.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "dataset_id" ], "properties": { "count": { "type": "integer", "default": 25, "maximum": 100, "minimum": 1 }, "format": { "enum": [ "csv", "geojson", "parquet" ], "type": "string", "default": "geojson" }, "dataset_id": { "type": "string", "maxLength": 80, "minLength": 1 } } }arguments 29 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id9c314d0b0323f33b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9c314d0b0323f33b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9c314d0b0323f33b?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.