hire-overseas
Registry code: dcbd1dec9739f832
Search remote professionals in the Philippines, Latin America and Africa; request introductions.
from a public catalogue that lists it, not from the operator
- endpoint
- https://api.hireoverseas.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 hire-overseas live?
- Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
- Is hire-overseas free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does hire-overseas have?
- 4 tools: search_candidates, get_request_status, get_candidate_resume, request_intro.
- Is hire-overseas 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
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
search_candidates unknown 13h ago
Searches Hire Overseas's pool of remote professionals in the Philippines, Latin America and Africa for a role and returns up to 5 anonymized profiles in seconds. Profiles show first name, country, skills and experience; never a surname, contact detail or employer name. Each profile has a candidateRef that get_candidate_resume and request_intro accept, says whether a resume exists, and includes a link to the candidate's intro video when there is one.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "roleTitle" ], "properties": { "skills": { "type": "array", "items": { "type": "string", "maxLength": 100 }, "maxItems": 30, "description": "Required skills or tools, e.g. ['QuickBooks', 'Xero']" }, "regions": { "type": "array", "items": { "enum": [ "ph", "latam", "africa" ], "type": "string" }, "description": "Limit to regions: ph (Philippines), latam (Latin America), africa. Omit for all." }, "roleTitle": { "type": "string", "maxLength": 200, "minLength": 2, "description": "e.g. 'Senior Bookkeeper' or 'Executive Assistant'" }, "description": { "type": "string", "maxLength": 10000, "description": "What the person will do, tools they need, hours. More detail gives better matches." }, "minYearsExperience": { "type": "integer", "maximum": 60, "minimum": 0 } } }arguments 46 linesget_request_status unknown 13h ago
Returns pending_review, approved or rejected for a request made with request_intro.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "requestId" ], "properties": { "requestId": { "type": "string" } } }arguments 12 linesget_candidate_resume unknown 13h ago
Returns the resume of a candidate from search_candidates as text, with the surname, contact details, links, employer names, city and referees removed. Available when the profile says resumeAvailable.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "candidateRef" ], "properties": { "candidateRef": { "type": "string", "description": "candidateRef from search_candidates" } } }arguments 13 linesrequest_intro unknown never probed
Requests an introduction to a candidate returned by search_candidates. The request goes to the Hire Overseas team, who verify the candidate, confirm availability and pricing, and reply to the contact email, usually within one business day. Requires the requester's real company name and work email. One request covers one candidate.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "candidateRef", "roleTitle", "clientName", "clientContact" ], "properties": { "message": { "type": "string", "maxLength": 2000 }, "roleTitle": { "type": "string", "maxLength": 200, "minLength": 2 }, "clientName": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Company that wants the candidate" }, "candidateRef": { "type": "string", "description": "candidateRef from search_candidates or recommend_candidates" }, "clientContact": { "type": "string", "format": "email", "pattern": "^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$", "maxLength": 200, "description": "The user's work email, where Hire Overseas replies" } } }arguments 38 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 iddcbd1dec9739f832.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dcbd1dec9739f832/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dcbd1dec9739f832?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.
- calls.hireoverseas.com calls.hireoverseas.com