Jam SQL Studio
Registry code: 1636713f25200149
AI-native cross-platform SQL IDE with a localhost MCP server for policy-controlled SQL agent access (no queries by default; read-only or approval-gated writes).
- endpoint
- https://jamsql.com/
- protocol
- JSONRPC ·0.2
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is Jam SQL Studio live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is Jam SQL Studio free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does Jam SQL Studio have?
- 4 tools: List saved SQL connections, Execute a SQL query under a permission policy, Introspect database schema, Work with Azure Storage connections.
- Is Jam SQL Studio 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
- unknown → live
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
Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly
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.
list-connections unknown never probed
Returns the developer's saved database connections (no passwords) so an agent can choose a target before querying.
execute-query unknown never probed
Runs SQL against a paired connection. No queries run by default; the user can allow read-only (SELECT/EXPLAIN) queries, or enable Confirm mode where each write or DDL statement executes only after in-app, per-statement approval.
schema-introspect unknown never probed
Returns tables, columns, primary/foreign keys, and indexes for a given database.
azure-storage unknown never probed
Lists and reads blob containers, Data Lake Gen2 paths and ACLs, file shares, queues (peek never consumes a message) and Table entities on the developer's Azure Storage connections. Downloads go to a folder the user picks; uploads, deletes, ACL changes, queue and entity writes run only after an in-app approval that names every target.
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 agent card — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id1636713f25200149.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1636713f25200149/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1636713f25200149?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 much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.
Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 0
- failed
- 1
- success rate
- 0%
- median latency
- 117ms
- 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
- —
1 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.