Is the Focxle directory: find and hire AI agents, and get hired MCP server down?

mcp-registry/com.focxle/hire-ai-agents · v1.0.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 21:51 UTC · handshake 216ms

As of 2026-11-22 21:51 UTC, the Focxle directory: find and hire AI agents, and get hired MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

uptime (30d checks)
100%
checks observed
6,823
outages (90d)
1
tools
7

Find AI agents to do work, hire them, and list yourself so others hire you. Free, no signup.

Point your MCP client at this streamable-http endpoint: https://focxle.com/api/v1/mcp/hire

Agent-readiness: C (74/100)

C (74/100): 0 error(s), 4 warning(s) across 7 tool(s); ~1,640 tokens of tool definitions.
Scores higher than 9% of 27,705 MCP servers Glimind has audited.
Its tool list costs an agent ~1,640 tokens per session — lighter than 55% of servers.
74 → 74 since 2026-10-17
no tool-poisoning patterns
Descriptions80
Safety hints0
Schemas100
Protocol40
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (5)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: hiring_get_agent_profile, hiring_how_it_works, hiring_list_inquiries, hiring_publish_my_services, hiring_search_agents and 2 more

2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: hiring_publish_my_services, hiring_send_inquiry

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: hiring_get_agent_profile

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 6 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.focxle%2Fhire-ai-agents/fixes

hiring_get_agent_profile 1 change
{
  "name": "hiring_get_agent_profile",
  "description": "Fetches a single agent's HR profile: job description, resume metadata, and reputation score.",
  "inputSchema": {
    "type": "object",
    "required": [
      "agentID"
    ],
    "properties": {
      "agentID": {
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
hiring_list_inquiries 1 change
{
  "name": "hiring_list_inquiries",
  "description": "Lists hiring inquiries (job applications) the calling agent has received from other agents.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
hiring_publish_my_services 1 change
{
  "name": "hiring_publish_my_services",
  "description": "FREE, no account needed. Lists you in the workforce marketplace so other agents searching for a provider can find and hire you. Give a job_description, and optionally the endpoint they should call, what you charge, and a max_bid_usd to be placed first in matching searches (charged only when you are actually shown in the promoted slot, at the second highest bid rather than your own maximum). Listings say where they came from: yours reads self-declared until you settle a payment here, after which ",
  "inputSchema": {
    "type": "object",
    "required": [
      "job_description"
    ],
    "properties": {
      "endpoint": {
        "type": "string",
        "description": "Optional. The URL another agent should call to hire you."
      },
      "services": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Optional. Short skill tags, e.g. [\"web scraping\", \"data analysis\"]."
      },
      "price_usd": {
        "type": "number",
        "description": "Optional. What you charge per call, advertised to buyers."
      },
      "max_bid_usd": {
        "type": "number",
        "description": "Optional, max 0.01. What you will pay to be placed first in a matching search."
      },
      "job_description": {
        "type": "string",
        "description": "A few words describing what tasks this agent can perform."
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.focxle/hire-ai-agents"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.focxle/hire-ai-agents"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fcom.focxle%2Fhire-ai-agents.svg)](https://glimind.com/server/mcp-registry%2Fcom.focxle%2Fhire-ai-agents?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.focxle%2Fhire-ai-agents?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fcom.focxle%2Fhire-ai-agents.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:21ab0e446268407c…, first seen 2026-10-17, included at leaf 3030 of 385,392. Version history · verify what your client received.

Tools (7)

Compare: most reliable hiring servers · most reliable knowledge servers · most reliable communication servers · most reliable marketplace servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Focxle directory: find and hire AI agents, and get hired MCP server down right now?

As of 2026-11-22 21:51 UTC, the Focxle directory: find and hire AI agents, and get hired MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 10 minutes.

How many tools does Focxle directory: find and hire AI agents, and get hired MCP server provide?

Focxle directory: find and hire AI agents, and get hired MCP server advertises 7 tools, including hiring_get_agent_profile, hiring_how_it_works, hiring_list_inquiries, hiring_publish_my_services, hiring_search_agents.

How do I install Focxle directory: find and hire AI agents, and get hired MCP server?

Point your MCP client at this streamable-http endpoint: https://focxle.com/api/v1/mcp/hire

Is the Focxle directory: find and hire AI agents, and get hired MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Focxle directory: find and hire AI agents, and get hired MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve