{"schema_version":1,"snapshot_id":"bfb936f5ceae4a7427f93961201723779c3021545a3c4222395e8678314c3e55","generated_at":"2026-10-17T21:51:24.907033+00:00","notice":"Potential GTM matches from directory metadata and model triage. Discovered does not mean vendor-verified or tested. Pending records remain under review; pricing and install details require primary sources.","canonical_url":"https://gtmmcps.com/discoveries/31ea73cb85b7f31f21cb","record":{"id":"31ea73cb85b7f31f21cb","name":"MCPulse","aliases":["MCPulse"],"description":"Analytics for MCP servers. Publish a server and you can see nothing — not how many people use it, which tools get called, whether the model understands your tool descriptions, or what your server costs the people using it. MCPulse answers that: calls, first-call success, retries, bad arguments, tool errors, crashes, empty results, latency and token cost, broken down per tool and per client. Install the [npm package](https://www.npmjs.com/package/@mcpulse/sdk) inside your own server and wrap it in two lines — no proxy, no DNS change, and your server keeps working if MCPulse is down","repository_url":null,"sources":[{"source_id":"smithery","url":"https://api.smithery.ai/servers","observed_at":"2026-10-17T21:40:22.481400+00:00","source_record_id":"1357a656-070f-492b-8583-31c4943f253a","source_record_name":"mcpulse/mcpulse"}],"relevance_signals":["analytics"],"classification":{"label":"pending","method":"not-yet-classified"},"catalog_ids":[],"verification_status":"discovered","vendor_ownership":"not-verified","execution_tested":false,"pricing_status":"not-verified","documentation_status":"not-verified"}}