crewai-marketing-site
Registry code: fd4411d239634283
Returns CrewAI marketing-site content: blog posts, customer case studies, events, webinars and links to developer documentation.
- endpoint
- https://crewai.com/mcp
- door code
- 045b85d53faa7620
- 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 crewai-marketing-site live?
- Yes — it answered the hub's last check (checked 51m ago). It answered 100% of checks over the last 30 days.
- Is crewai-marketing-site free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does crewai-marketing-site have?
- 5 tools: crewai_developer_resources, crewai_list_blog_posts, crewai_list_case_studies, crewai_list_events, crewai_list_webinars.
- Is crewai-marketing-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.1%· all time 99.1%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- degraded → live
- topic
- knowledge & reference
- used for
- list a company's blog posts
- list customer case studies
- list upcoming events and webinars
- get developer documentation links
- takes → gives
- text → data
- tools
- 5 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.
crewai_list_case_studies reads open 4h ago
Returns paginated customer case studies (same data as GET /api/case-studies).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "skip": { "type": "integer", "minimum": 0 }, "limit": { "type": "integer", "maximum": 24, "minimum": 1 }, "excludeFeatured": { "type": "string" } }, "additionalProperties": false }arguments 19 linescrewai_list_events reads open 4h ago
Returns paginated events (same data as GET /api/events).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "skip": { "type": "integer", "minimum": 0 }, "limit": { "type": "integer", "maximum": 24, "minimum": 1 }, "category": { "type": "string" } }, "additionalProperties": false }arguments 19 linescrewai_list_webinars reads open 4h ago
Returns paginated webinars (same data as GET /api/webinars).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "skip": { "type": "integer", "minimum": 0 }, "limit": { "type": "integer", "maximum": 24, "minimum": 1 }, "category": { "type": "string" } }, "additionalProperties": false }arguments 19 linescrewai_developer_resources reads unknown never probed
Returns canonical URLs for CrewAI staging developer docs: OpenAPI, auth, webhooks, MCP, and portal.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linescrewai_list_blog_posts reads unknown never probed
Returns paginated blog posts from the CrewAI marketing site public API (same data as GET /api/blog-posts).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "skip": { "type": "integer", "minimum": 0 }, "limit": { "type": "integer", "maximum": 24, "minimum": 1 }, "category": { "type": "string" } }, "additionalProperties": false }arguments 19 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 idfd4411d239634283.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fd4411d239634283/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fd4411d239634283?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.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- docs.crewai.com CrewAI
- docs-platform.crewai.com CrewAI Platform