latina-dev
Registry code: 4d79d40880b60246
Latina Dev (https://latina.dev) is a directory of Latina software engineers at the student, individual contributor and leadership levels, plus a curated list of communities, programs, job boards, conferences and reads for Latina engineers.
Use search_members to find Latina engineers by name, company, school, location, country of heritage or what they are open to (mentoring, speaking, job opportunities and more), and get_member for one full profile. Use search_resources and list_resource_categories to find communities and resources. Link people to the profile or resource URLs in the results.
- endpoint
- https://latina.dev/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 latina-dev live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is latina-dev free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does latina-dev have?
- 4 tools: get_member, list_resource_categories, search_members, search_resources.
- Is latina-dev 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 100%· all time 100%
last good check
of 4 tools
- unknown → live
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_resource_categories open 1h ago
List the resource categories on latina.dev/resources, such as communities, K-12 and college programs, job boards and conferences, with how many resources each has.
{ "type": "object", "properties": {} }arguments 4 linessearch_members open 1h ago
Search the Latina Dev directory of Latina software engineers. Every keyword in `query` must match the member's name, title and company or school, location, countries of heritage, level, what they are open to or bio. Filters narrow results further. Leave everything empty to list members. Returns public profile fields and the profile URL.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "level": { "enum": [ "Student", "Individual Contributor", "Leader" ], "type": "string", "description": "Career level" }, "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Most results to return, 1 to 50 (default 20)" }, "query": { "type": "string", "description": "Keywords, e.g. \"Google\", \"Austin\", \"frontend\", \"Stanford\"" }, "country": { "enum": [ "Argentina", "Belize", "Bolivia", "Brazil", "Chile", "Colombia", "Costa Rica", "Cuba", "Dominican Republic", "Ecuador", "El Salvador", "Guatemala", "Haiti", "Honduras", "Mexico", "Nicaragua", "Panama", "Paraguay", "Peru", "Puerto Rico", "Uruguay", "Venezuela" ], "type": "string", "description": "Country of heritage" }, "open_to": { "enum": [ "Mentoring", "Being mentored", "Job opportunities", "Speaking", "Hiring" ], "type": "string", "description": "What the member is open to" } } }arguments 64 linessearch_resources open 1h ago
Search the communities, student programs, scholarships, job boards, career and leadership groups, conferences, founder support, podcasts, newsletters and reports that Latina Dev lists for Latina software engineers. Every keyword in `query` must match a resource's name, description or category. Leave it empty to list everything in a category.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "integer", "maximum": 50, "minimum": 1, "description": "Most results to return, 1 to 50 (default 20)" }, "query": { "type": "string", "description": "Keywords, e.g. \"mentorship\", \"scholarship\", \"podcast\", \"cybersecurity\"" }, "category": { "enum": [ "latina-communities", "latino-tech-communities", "k-12", "college", "jobs", "career-growth", "conferences", "founders", "listen-and-read" ], "type": "string", "description": "Category id from list_resource_categories" } } }arguments 31 linesget_member unknown never probed
Get one Latina Dev member's public profile by slug, the last part of their profile URL (https://latina.dev/members/<slug>).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Profile slug, e.g. \"frances-coronel\"" } } }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 id4d79d40880b60246.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d79d40880b60246/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4d79d40880b60246?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.