jesseg-io
Registry code: 803524bf662d155b
Personal site of Jesse Gabriellini exposing his writing, RSS feed, project entity graph and paid playbooks sold via x402.
- endpoint
- https://jesseg.io/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 jesseg-io live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is jesseg-io free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does jesseg-io have?
- 8 tools: list_playbooks, get_playbook_full, get_entity_graph, get_x402_manifest, get_site_context, get_health_status, get_feed, search_writing.
- Is jesseg-io 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 99.1%· all time 99.1%
last good check
of 8 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- knowledge & reference
- used for
- search a personal blog's writing
- get a site owner's project graph
- buy a paid playbook
- takes → gives
- text → data, text
- tools
- 8 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.
get_entity_graph reads open 13h ago
Return Entity Graph v2 JSON for Jesse Gabriellini and the public project network
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_x402_manifest reads open 21h ago
Return the x402 manifest with paid playbook endpoints and buyer policy.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_site_context reads open 21h ago
Return llms.txt factual site context for jesseg.io
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_health_status reads open 13h ago
Return GET /api/health JSON status payload
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_feed reads open 13h ago
Return syndicated writing RSS feed XML
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessearch_writing reads open 21h ago
Search writing slugs and topics. Omit query to list all slugs and topic labels.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "query": { "type": "string", "description": "Topic keyword or slug fragment" } } }arguments 10 lineslist_playbooks reads unknown never probed
Return the free playbook catalog (slug, price, preview URL). Call before get_playbook_full.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_playbook_full reads unknown never probed
Fetch full structured playbook JSON via x402. Returns 402 payment instructions when unpaid. Call GET /.well-known/x402 first.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Playbook slug, e.g. phc-system-teardown or ai-citation-network" } } }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 id803524bf662d155b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/803524bf662d155b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/803524bf662d155b?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.