PulseGate
REMOTE · WWW.PULSEGATE.AI
Bounded software search, unknown requirements, and the origins of project identifiers.
Available components
Last scanned (5 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 598 tokens (~199/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 +1
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +55
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.53 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.pulsegate.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pulsegate.ai | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 220cc46e604652d70e3157ef2ce271ee |
| SANs: pulsegate.ai, *.pulsegate.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.pulsegate.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| pulsegate.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://*.posthog.com https://*.i.posthog.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://*.posthog.com https://*.i.posthog.com https://*.ingest.sentry.io https://*.sentry.io; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; report-uri /api/csp-report |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.pulsegate.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.pulsegate.ai/api/mcp | HTTPS enforced | 308 | https://www.pulsegate.ai/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_identifier_platforms List supported identifier platforms ~42
List every platform PulseGate records identifiers on, with how many identifiers it holds for each. Use it to learn the vocabulary the platform argument of lookup_project accepts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lookup_project Read a project's identifier evidence ~127
Return the external identifiers PulseGate holds for one project, and for each one how it arrived and whether anyone has checked that it belongs. Makes no claim about whether the software is alive, maintained, or working. Look up by slug, or by an identifier you already have.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | Identifier platform to look up by, e.g. "github_repo" or "npm_package". Use with value. |
| slug | string | – | The PulseGate slug of the listing. |
| value | string | – | The identifier on that platform, e.g. owner/name for github_repo. |
No output schema declared.
No examples provided.
search_catalog Find software for a task ~233
Find software by name, task or recorded filters. Returns at most ten candidates from the same service as native HTML/HTTP search, with recordUrl and met/unmet/unknown requirement assessments. Unknown is not false. No complete profile, publisher fetch, bulk export or functionality guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Recorded category slug, including its descendants. |
| license | string | – | Recorded license family, not a verified legal conclusion. |
| limit | integer | – | Same normalization as HTTP search; at most ten combined identities. |
| page | integer | – | Same normalization as HTTP search; depth beyond 50 is refused. |
| platform | string | – | Recorded platform filter, using the HTTP search vocabulary. |
| pricing | string | – | Recorded pricing classification, not proof of a price. |
| q | string | – | Name or task; at most 512 UTF-8 bytes and 12 words. No model or translation is called. |
| require | string | – | Up to three requirements, e.g. api:true,mcp:true. Missing or inferred evidence stays unknown. |
| unknown | string | – | Defaults to include candidates needing verification. |
No output schema declared.
No examples provided.
How do I install the PulseGate MCP server?
PulseGate is a hosted endpoint at https://www.pulsegate.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.pulsegate.ai
claude mcp add --transport http ai-pulsegate-provenance 'https://www.pulsegate.ai/api/mcp'
What is the PulseGate MCP server?
PulseGate is an MCP server listed in the public MCP registry as ai.pulsegate/provenance. Bounded software search, unknown requirements, and the origins of project identifiers. This page covers its hosted endpoint (https://www.pulsegate.ai/api/mcp).
Is the PulseGate MCP server safe to use?
PulseGate scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the PulseGate MCP server expose?
PulseGate exposes 3 tools: search_catalog, lookup_project, list_identifier_platforms. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Does the PulseGate MCP server require authentication?
No. We connected to PulseGate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PulseGate MCP server still maintained?
PulseGate is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.