com.gqlteam/site
Registry code: d7237a312032d3ff
Read-only access to gqlteam.com: services, case studies, articles, ventures and contact details of software architect Dan Podina. Use search first when unsure which slug to fetch.
- endpoint
- https://mcp.gqlteam.com/mcp
- protocol
- http-sse ·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 com.gqlteam/site live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is com.gqlteam/site free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does com.gqlteam/site have?
- 10 tools: get_contact_and_booking, get_article, get_case_study, search, get_service, list_articles, get_profile, get_ventures, ….
- Is com.gqlteam/site 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.3%· all time 99.3%
last good check
of 10 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- productivity & business
- used for
- read a software architect's services and case studies
- read articles
- get contact and booking details
- takes → gives
- text → text, data
- tools
- 10 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.
list_articles reads open 3h ago
Blog articles, newest first, with publication date, tags and reading time.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_profile reads open 3h ago
Who Dan Podina is: role, company, location, expertise, current roles, links, contact details and the ventures he runs.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_ventures reads open 3h ago
The products and open source projects Dan Podina runs, with role and links.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 lineslist_services reads open 8h ago
Every consulting service offered, with the slug to pass to get_service.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 lineslist_case_studies reads open 8h ago
Case studies and shipped projects, with industry, technologies, headline metrics and current status.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_contact_and_booking reads unknown never probed
How to get in touch: email, phone, the booking link for a free 30 minute review, contact page, response time and location.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesget_article reads unknown 13h ago
One article in full, including the complete post body as Markdown.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "slug" ], "properties": { "slug": { "type": "string", "minLength": 1, "description": "Article slug, for example owasp-asvs-levels" } } }arguments 14 linesget_case_study reads unknown 13h ago
One case study in full, including the complete page body as Markdown.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "slug" ], "properties": { "slug": { "type": "string", "minLength": 1, "description": "Case study slug, for example labrago or sabra" } } }arguments 14 linessearch reads unknown 13h ago
Search services, case studies and articles by keyword. Returns ranked matches with a snippet and the slug to fetch next.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "query" ], "properties": { "limit": { "type": "integer", "default": 8, "maximum": 20, "minimum": 1, "description": "Maximum number of results" }, "query": { "type": "string", "minLength": 2, "description": "Search terms, for example HIPAA or Apollo Federation" } } }arguments 21 linesget_service reads unknown 8h ago
One service in full: headline stats, FAQ, the offer, and the complete page body as Markdown.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "slug" ], "properties": { "slug": { "type": "string", "minLength": 1, "description": "Service slug, for example compliance or graphql-architecture" } } }arguments 14 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 idd7237a312032d3ff.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/d7237a312032d3ff/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/d7237a312032d3ff?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.