PulseGate
MCP server · www.pulsegate.ai · found in a public registry · checked since 2026-10-17
Live, handshake completed · latest check
Lists a project's external identifiers across platforms and whether each has been verified.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means
Placed in Developer data: Package registries, versions, repositories, changelogs and other developer data.
GET https://www.pulsegate.ai/api/mcpThe name is the registry's label, not ours. Not reviewed by a person.
Our checks
An unpaid request daily, from eastern North AmericaLast 3 checks, oldest to newest; room for 27 more
1 passed, 2 failed, 27 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Details
Tools listed by the server
list_identifier_platformslookup_projectsearch_catalog
- Tools
- 3
- This list since
- 2026-10-19
- First listed to us
- 2026-10-19
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/1); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Compute, code and storage / Developer data (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-19. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/5): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, MCP endpoint answered HTTP 200 | 931 ms |
cloudflare:MIA |
Timed out no response within 10000 ms |
— |
cloudflare:ATL |
Timed out no response within 10000 ms |
— |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/1) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. The registry's description is not republished.
- Limited evidence: monitored for 4 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_64e2c483799fb75f