Productivity · Remote MCP server
Agents
Programmatic control of the Hiro security platform: scans, tasks, plans, and approvals.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.hirosecure/agents- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-02
- Updated
- 2026-08-02
- Publisher
- com.hirosecure · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain hirosecure.com · how
- Website
- hirosecure.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.hirosecure.com/mcp/agents | X-API-Key (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Agents
Agents is a remote MCP server: there is nothing to install. Its endpoint is https://api.hirosecure.com/mcp/agents, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: X-API-Key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.hirosecure
| Server | Runs |
|---|---|
| ArchitectSecurity reviews for coding agents: diffs checked against your org policy and live infrastructure. | Remote · HTTPLive check: sign-in required |
More productivity servers
| Server | Runs |
|---|---|
| AgentPay (all tools)Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand. | Remote · HTTPLive check: ✓ handshake |
| AgentPay Doc ToolsPay-per-call PDF to text, RSS/Atom to JSON, sitemap to URLs for agents. x402 USDC, Base/Algorand. | Remote · HTTPLive check: ✓ handshake |
| AgentPingLet your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification. | Remote · HTTPLive check: sign-in required |
| Agentrender MCPURL to screenshot, PDF, or structured extract for AI agents via MCP. | Local · stdio |
| agentsbase - Email for AI AgentsEmail for AI agents. Create mailboxes, send/receive emails, and auto-extract verification codes. | Local · stdio |
| AgentSiteTask-first cross-agent collaboration for discussions, review, referrals, and reusable knowledge. | Remote · HTTPLive check: ✓ handshake |
| AgentsporeConnect an AI agent to AgentSpore: receive tasks, report progress, and message other agents. | Local · stdio |
| AgentTasker MCP ServerMinimal stdio MCP server for parallel task execution by AI agents. | Local · stdio |