_ registry / mcp + a2a JSONRPC · checked 2h ago

StudioMeyer Crew

listed under this name in a public catalogue; the server gives only its address, crew.studiomeyer.io

https://crew.studiomeyer.io

Registry code: b4095e3f1737a8e4

api record

Agent Personas for Claude. 10 tools, 8 personas, 3 workflows. Zero API cost.

from a public catalogue that lists it, not from the operator

endpoint
https://crew.studiomeyer.io/mcp
door code
6610d4b80f25d15a
protocol
JSONRPC ·0.3
authentication
bearer
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is StudioMeyer Crew live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is StudioMeyer Crew free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does StudioMeyer Crew have?
8 tools: Activate expert persona, Rate persona quality, Provider-agnostic personas, Multi-tenant SaaS with app-layer isolation, List available personas, Run a multi-persona workflow, Create custom persona (Pro), Optional Memory bridge.
Is StudioMeyer Crew 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.
reachable
live
uptime, 30 days
100%

90 days 99.5%· all time 99.3%

latency
199ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 828 checks · signed record
  • down → live
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
ai & agents
used for
  • apply an agent persona
  • run persona workflows
takes → gives
text → text
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
8 auth-required 8 of 8 classified

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.

  • persona-activation auth-required never probed

    Switch the LLM into a specialist role: CEO, CFO, CTO, CMO, PM, Analyst, Support, Creative Director (free tier) plus Legal Advisor, Sales Engineer, Data Scientist, UX Researcher, Developer Relations (Pro tier). Each persona brings frameworks, decision rules, output formats.

    personaactivationroles

  • persona-feedback auth-required never probed

    Track which personas worked well for which tasks. Feedback drives recommendation engine + future persona library improvements.

    feedbackqualityanalytics

  • multi-llm-personas auth-required never probed

    Personas are SYSTEM-PROMPT layers — they work with ANY LLM that speaks MCP: Claude, GPT, Gemini, Mistral, Grok, local models. Zero LLM API cost on our side, you bring your own LLM, we provide the persona logic.

    multi-llmagnosticmcpbyo-llm

  • tenant-isolation auth-required never probed

    Custom personas + workflows + usage stats are tenant-scoped: every query carries the tenant id in its WHERE clause, and there is no name→tenant resolver. API keys are HMAC-SHA256 hashed with a server-side pepper. EU Nürnberg (own PostgreSQL).

    multi-tenantisolationgdpr

  • persona-list auth-required never probed

    13 personas total (8 free + 5 Pro). Returns name, role, expertise areas, output format. Filter by tier or domain.

    personadiscoverycatalog

  • multi-persona-workflow auth-required never probed

    Three pre-built workflows that chain personas: strategy-review (CEO → CFO → CTO), content-pipeline (CMO → Analyst → Creative), product-launch (Analyst → PM → CEO → CMO → CTO). Returns synthesized output.

    workflowchainorchestration

  • custom-persona auth-required never probed

    Author a custom persona in cloud-stored Markdown with frontmatter. Reusable across sessions. Shareable within team workspace.

    personacustomauthoringpro

  • memory-bridge auth-required never probed

    Personas can read + write to StudioMeyer Memory if API key configured. Enables persona-specific context (CFO sees only finance memories, etc.) and continuity across sessions.

    memorybridgeintegrationcontext

_ try it over a2a through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b4095e3f1737a8e4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b4095e3f1737a8e4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b4095e3f1737a8e4/badge.svg)](https://brick.blue/agent/b4095e3f1737a8e4?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 we knowoff the mcp door
card completeness
20%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.

_ also on studiomeyer.io 4 entries

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.