ipinfo

Subscribe to Alerts

subscribe

Idempotent

Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"you@x.com"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).

Input Schema

TableJSON Schema

Name	Required	Description
`type`	Yes	Subscription type.
`params`	Yes	Type-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}. clinical_trial: {sponsor?:"Pfizer", condition?:"lung cancer", phase?:"PHASE3"} (sponsor or condition required).
`delivery`	No	Optional delivery channels in addition to the always-on persistent feed. {email:"you@x.com"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:"https://..."} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of "<X-Pipeworx-Timestamp>.<raw body>". Auto-disabled after 10 consecutive failing runs.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJun 10, 2026

changedInput schema / properties / delivery / description

Previous value: -"Optional delivery channels in addition to the always-on persistent feed. {email:\"you@x.com\"} sends a templated alert per fired event. {sms:\"+15551234567\"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first). Capped at 10 SMS/day per subscription."New value: +"Optional delivery channels in addition to the always-on persistent feed. {email:\"you@x.com\"} sends a templated alert per fired event. {sms:\"+15551234567\"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first; 10/day cap). {webhook:\"https://...\"} POSTs each event JSON to your endpoint, HMAC-signed — the response includes delivery.webhook_secret (whsec_…) ONCE; verify X-Pipeworx-Signature = sha256 HMAC of \"<X-Pipeworx-Timestamp>.<raw body>\". Auto-disabled after 10 consecutive failing runs."

addedInput schema / properties / delivery / properties / webhook

Added value: +{
+  "description": "HTTPS URL to POST fired events to. https only; localhost/private hosts rejected. Signing secret returned once at subscribe time.",
+  "type": "string"
+}

Changed2 schema fields changedJun 10, 2026

changedInput schema / properties / params / description

Previous value: -"Type-specific filter. sec_8k: {ticker:\"AAPL\", items?:[\"5.02\",\"1.01\"]}. polymarket_edge: {topic:\"fed\", min_spread_bps?:500}. fred_series: {series_id:\"UNRATE\"}. patent_grant: {applicant:\"Apple Inc.\"} (use exact corporate form — match is approximate so wrong suffix returns the whole pool; payload flags the case)."New value: +"Type-specific filter. sec_8k: {ticker:\"AAPL\", items?:[\"5.02\",\"1.01\"]}. polymarket_edge: {topic:\"fed\", min_spread_bps?:500}. fred_series: {series_id:\"UNRATE\"}. patent_grant: {applicant:\"Apple Inc.\"}. clinical_trial: {sponsor?:\"Pfizer\", condition?:\"lung cancer\", phase?:\"PHASE3\"} (sponsor or condition required)."

changedInput schema / properties / type / enum

Previous value: -[
-  "sec_8k",
-  "polymarket_edge",
-  "fred_series",
-  "patent_grant"
-]New value: +[
+  "sec_8k",
+  "polymarket_edge",
+  "fred_series",
+  "patent_grant",
+  "clinical_trial"
+]

Changed3 schema fields changedJun 10, 2026

changedInput schema / properties / params / description

Previous value: -"Type-specific filter. For sec_8k: {ticker:\"AAPL\", items?:[\"5.02\",\"1.01\"]}. items defaults to all if omitted."New value: +"Type-specific filter. sec_8k: {ticker:\"AAPL\", items?:[\"5.02\",\"1.01\"]}. polymarket_edge: {topic:\"fed\", min_spread_bps?:500}. fred_series: {series_id:\"UNRATE\"}. patent_grant: {applicant:\"Apple Inc.\"} (use exact corporate form — match is approximate so wrong suffix returns the whole pool; payload flags the case)."

changedInput schema / properties / type / description

Previous value: -"Subscription type. v1: \"sec_8k\"."New value: +"Subscription type."

changedInput schema / properties / type / enum

Previous value: -[
-  "sec_8k"
-]New value: +[
+  "sec_8k",
+  "polymarket_edge",
+  "fred_series",
+  "patent_grant"
+]

Changed2 schema fields changedJun 9, 2026

changedInput schema / properties / delivery / description

Previous value: -"Optional delivery channels in addition to the always-on persistent feed. {email:\"you@x.com\"} sends a templated alert per fired event. Future: sms, webhook."New value: +"Optional delivery channels in addition to the always-on persistent feed. {email:\"you@x.com\"} sends a templated alert per fired event. {sms:\"+15551234567\"} sends an SMS per event — must match the verified phone on the caller's account (verify at https://pipeworx.io/account first). Capped at 10 SMS/day per subscription."

addedInput schema / properties / delivery / properties / sms

Added value: +{
+  "description": "E.164 phone number, e.g. \"+15551234567\". Must match the account's verified phone.",
+  "type": "string"
+}

Changed1 schema field changedJun 9, 2026

addedInput schema / properties / delivery

Added value: +{
+  "description": "Optional delivery channels in addition to the always-on persistent feed. {email:\"you@x.com\"} sends a templated alert per fired event. Future: sms, webhook.",
+  "properties": {
+    "email": {
+      "description": "Email address to deliver alerts to. Validated against a standard pattern.",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedJun 9, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description goes far beyond the annotations (non-read-only, open-world, idempotent, non-destructive). It details OAuth requirements, SMS verification with a 10/day cap, webhook HMAC signing and auto-disable after 10 failing runs, and the always-on feed behavior. This provides essential context for an agent to understand side effects and constraints, with no contradictions to annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single dense paragraph, but the length is justified given the 5 subscription types and multiple delivery channels. It front-loads the primary action and return value, and each sentence adds necessary detail. Minor inefficiency exists in repeating some schema information, but it remains structured enough for an agent to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with no output schema, the description covers all critical dimensions: OAuth prerequisites, all supported types with examples, delivery channels (feed, email, SMS, webhook), rate limits, verification requirements, and the returned subscription ID. It also explains how to consume the feed. There are no major gaps that would confuse an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already has 100% coverage, but the description adds interpretive meaning beyond the schema. For example, it explains that items:["5.02"] corresponds to an officer change and clarifies what polymarket_edge mispricings are. These concrete examples help the agent construct valid params, even though much of the delivery schema is already self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id.' This is a specific verb+resource with a clear output. It distinguishes from sibling tools like list_subscriptions, unsubscribe, and recent_alerts by focusing on creation and ongoing subscription behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context: requires a Pipeworx OAuth account, lists supported subscription types, and explains delivery channels. It mentions pulling via recent_alerts as part of the feed behavior, implying an alternative consumption mode. However, it does not explicitly compare against sibling tools like list_subscriptions or unsubscribe for management tasks, so it lacks explicit when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ipinfo tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer data questions; polymarket_arbitrage, polymarket_edges, and polymarket_edge_tracker all scan prediction markets. Despite long descriptions, an agent could easily select the wrong one, especially the currently identical ask_pipeworx and ask_pipeworx_beta.

Naming Consistency3/5

Mostly snake_case, but with inconsistent patterns: get_my_ip/lookup_ip use verb_noun, entity_profile/recent_changes are noun phrases, remember/recall/forget are bare verbs, and the polymarket_* tools share a brand-prefixed noun style. Readable but not a predictable, uniform convention.

Tool Count2/5

At 33 tools, the server is overloaded, far exceeding the 25-tool threshold for 'too many.' It combines two unrelated identities—the original ipinfo IP lookup and the massive Pipeworx data/research platform—making the toolset heavy and harder for an agent to navigate efficiently.

Completeness4/5

The tool surface provides strong coverage of the data query and research lifecycle: discovery (discover_tools, suggest_questions), entity resolution (resolve_entity), lookup (ask_pipeworx, entity_profile), verification (validate_claim, ask_pipeworx_grounded), and post-processing (search_within, recent_changes). Minor gaps exist—for example, no dedicated 'get SEC filing by accession' tool or single-purpose financials endpoint—but these are workaroundable via the routing tools.

Subscribe to Alerts

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources