jooq-documentation-mcp
https://jooq-mcp.martinelli.ch
Registry code: 1b1449809132e0b5
An MCP server that provides access to the jOOQ documentation
from a public catalogue that lists it, not from the operator
- endpoint
- https://jooq-mcp.martinelli.ch/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 jooq-documentation-mcp live?
- Yes — it answered the hub's last check (checked 10m ago). It answered 98% of checks over the last 30 days.
- Is jooq-documentation-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does jooq-documentation-mcp have?
- 6 tools: getAdvancedFeatures, getDatabaseSupport, searchDocumentation, getQueryDslReference, getSqlExamples, getCodeGenerationGuide.
- Is jooq-documentation-mcp 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 98.1%· all time 98.1%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search jooq documentation
- get sql query building examples
- get code generation guide
- takes → gives
- text → text
- tools
- 6 reads
- note
- documentation mirror
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.
getCodeGenerationGuide reads open 9h ago
Get jOOQ code generation guide and configuration examples
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [], "properties": {}, "additionalProperties": false }arguments 7 linesgetAdvancedFeatures reads unknown 9h ago
Get information about jOOQ's advanced features like transactions, stored procedures, or batch operations
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "feature" ], "properties": { "feature": { "type": "string" } }, "additionalProperties": false }arguments 13 linesgetDatabaseSupport reads unknown never probed
Get database-specific support information and SQL dialect details for a specific database (e.g., MySQL, PostgreSQL, Oracle, SQL Server)
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "database" ], "properties": { "database": { "type": "string" } }, "additionalProperties": false }arguments 13 linessearchDocumentation reads unknown 9h ago
Search jOOQ documentation for specific topics, features, or SQL operations. Returns relevant documentation sections.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "query": { "type": "string" } }, "additionalProperties": false }arguments 13 linesgetQueryDslReference reads unknown 2h ago
Get jOOQ Query DSL reference for specific query types (e.g., SELECT, INSERT, UPDATE, DELETE, MERGE)
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "queryType" ], "properties": { "queryType": { "type": "string" } }, "additionalProperties": false }arguments 13 linesgetSqlExamples reads unknown never probed
Get SQL query building examples for a specific topic (e.g., SELECT, INSERT, UPDATE, DELETE, JOIN, subqueries)
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "topic" ], "properties": { "topic": { "type": "string" } }, "additionalProperties": false }arguments 13 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 id1b1449809132e0b5.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/1b1449809132e0b5/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/1b1449809132e0b5?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.