Skip to main content
Glama

Phishtank

by io.github.pipeworx-io

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
NameRequiredDescriptionDefault
typeYesSubscription type.
paramsYesType-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).
deliveryNoOptional 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.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The description adds extensive behavioral details beyond the minimal annotations: it requires an OAuth account, returns the new subscription id, explains webhook HMAC signing and the 'whsec_' secret returned only once, describes automatic webhook disabling after 10 failures, SMS verification and a 10/day cap. This significantly exceeds the annotations' safety profile and provides actionable operational knowledge.

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

Conciseness5/5

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

The description is dense yet perfectly structured: it front-loads the core purpose, then logically proceeds through return value, prerequisites, types, and delivery channels. Every sentence carries essential information without repetition or filler, making it an efficient and well-organized explanation for a complex tool.

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?

Given the tool's complexity (3 parameters, 5 types, nested delivery object, no output schema), the description is remarkably complete. It explains the return value, authentication requirements, all delivery channels including their restrictions, and even mentions how to pull from the feed via recent_alerts or GET registry. It leaves no critical operational question unanswered.

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?

Schema coverage is 100% and already documents each parameter, but the description enriches semantics with concrete examples like 'items:["5.02"] = officer change' and delivery behavior (e.g., webhook auto-disable). It does not cover all five types in the description (patent_grant, clinical_trial are only in schema), but for the types it does cover, it adds meaning beyond the schema.

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 first sentence clearly states the action: 'Create a proactive monitoring subscription to a live-data event stream.' This specifies the verb (create), resource (subscription), and purpose (monitoring). It distinguishes from sibling tools like list_subscriptions, unsubscribe, and recent_alerts by focusing on subscription creation rather than listing, removing, or reading alerts.

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 for when to use the tool, including prerequisites ('Requires a Pipeworx OAuth account'), supported subscription types, and delivery channel options. However, it does not explicitly state when not to use it or mention alternatives (e.g., for managing existing subscriptions, use list_subscriptions/unsubscribe), so it falls short of a 5.

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

All Phishtank toolsInspect
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

B3.4/5.0
Disambiguation1/5

The server is named 'Phishtank' but only one tool (check_url) relates to phishing. The remaining 31 tools cover a wide range of unrelated topics (data research, prediction markets, memory, etc.), many with overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research). This makes it extremely difficult for an agent to select the right tool.

Naming Consistency2/5

Tool names mix conventions inconsistently: some use underscores (ai_visibility_check, check_url), some are camelCase (ask_pipeworx, bet_research), and others are compound phrases. There is no predictable pattern across the set.

Tool Count1/5

With 32 tools, the count is high, but only one aligns with the server name 'Phishtank' (check_url). The vast majority belong to an entirely different domain (Pipeworx tools), making the tool count severely inappropriate for the server's stated purpose.

Completeness1/5

For a phishing detection server, the tool surface is severely incomplete. It lacks essential tools like report_phish, verify_phish, get_stats, etc. The single phishing tool (check_url) is insufficient, while the other 31 tools are completely out of scope.

Resources