MCP servers › io.github.pipeworx-io › alaska-code
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.pipeworx-io/alaska-code
Alaska Statutes — statute text by citation and chapter-catchline search. Fleet #2795. — the publisher's description
Summary
io.github.pipeworx-io/alaska-code is a remote MCP server listed in the official MCP registry at version 0.1.3. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 44 tools, 0 resources and 12 prompts.
Record checks
4 of 5 record checks met · 4 do not apply
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Repository
- public
- Tools
- 44
- Described as changing data
- 4 of 44 toolsAI-classified
- Topic
- data-and-databasesAI-classified
- Pricing
- usage-basedAI-classified
- Last tested
- 2026-10-23
Observed fact
This server accepted a session without any credential and lists 1 tool whose name or declaration suggests it changes data (forget). That is our reading of the names; we did not call it. Source: our connection, 2026-10-23.
Worth knowing before you connect it
- 4 tools are described as changing something (subscribe, unsubscribe, pipeworx_feedback, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 0.1.3, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-07 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 4 versions listed, 2026-10-07 to 2026-10-22; 4 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 4 versions
0.1.3· 2026-10-220.1.2· 2026-10-200.1.1· 2026-10-190.1.0· 2026-10-07
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.1.3 (published 2026-10-22).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventory4 of 44 tools are described as changing something (creating, editing, deleting, sending or running). For 4 the reading was uncertain, so no mark is shown.
“PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinica…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs, 1 required
questionstringrequired“Your question or request in natural language.”querystring“Alias for question.”qstring“Alias for question.”promptstring“Alias for question.”textstring“Alias for question.”inputstring“Alias for question.”askstring“Alias for question.”messagestring“Alias for question.”packsarray“OPTIONAL.”
“Beta version of ask_pipeworx: identical universal router (same 7,096 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs, 1 required
questionstringrequired“Your question or request in natural language.”querystring“Alias for question.”qstring“Alias for question.”promptstring“Alias for question.”textstring“Alias for question.”inputstring“Alias for question.”askstring“Alias for question.”messagestring“Alias for question.”packsarray“OPTIONAL.”
“Hallucination-resistant answer mode for high-stakes reads.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs, 1 required
questionstringrequired“Your question in natural language.”querystring“Alias for question.”qstring“Alias for question.”promptstring“Alias for question.”textstring“Alias for question.”inputstring“Alias for question.”askstring“Alias for question.”messagestring“Alias for question.”prefer_toolstring“Run this exact tool instead of letting the router choose — use a name from a previous answer's alternatives[].”
“Semantic search INSIDE a fetched record.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
textstringrequired“The document text to search inside (max ~200K chars).”querystringrequired“Natural-language query — what passages do you want?”limitnumber“Max passages to return (1-20, default 5).”
“ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs, 1 required
questionstringrequired“The research question, in natural language.”querystring“Alias for question.”qstring“Alias for question.”promptstring“Alias for question.”textstring“Alias for question.”inputstring“Alias for question.”askstring“Alias for question.”messagestring“Alias for question.”depthstring“How many facets to research in parallel: quick=3 (single hop), standard=3 (default; adds a gap-recovery hop that re-angles unanswered facets + a contradictions…”
“Find tools by describing the data or task.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs, 1 required
querystringrequired“Natural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries").”taskstring“Alias for query.”qstring“Alias for query.”descriptionstring“Alias for query.”searchstring“Alias for query.”limitnumber“Maximum number of tools to return (default 20, max 50)”
“"What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
typestringrequired“Entity type: "company" or "drug".”valuestringrequired“For company: ticker (AAPL), CIK (0000320193), or name.”countrystring“OPTIONAL ISO 3166-1 alpha-2 of the country whose business register you mean ("NO", "FI", "JP", "GB", "FR", "EE", "BR").”
“"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ON…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
typestringrequired“Entity type: "company" or "drug".”valuesarrayrequired“For company: 2–5 tickers/CIKs (e.g., ["AAPL","MSFT"]).”
“Create a proactive monitoring subscription to a live-data event stream.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
typestringrequired“Subscription type.”paramsobjectrequired“Type-specific filter.”deliveryobject“Optional delivery channels in addition to the always-on persistent feed.”
“Cancel a subscription by id.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
1 input, 1 required
idstringrequired“Subscription id (uuid) returned by subscribe.”
“List the caller's active subscriptions.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
include_inactiveboolean“Include cancelled subscriptions in the response (default false).”
“Pull fired events from your subscription feed.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
typestring“Optional — filter to one subscription type.”sincestring“Optional ISO timestamp — return events fired_at >= this time.”limitnumber“Max events to return (1-200, default 50).”unread_onlyboolean“Return only events where read_at is null (default false).”mark_readboolean“Flag the returned events read in the same call (default false).”
Show 32 more tools
“"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-s…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
typestringrequired“"company" or "ticker" — both are accepted and behave identically; `value` can be a ticker, CIK, or company name either way.”valuestringrequired“Ticker (e.g., "AAPL"), zero-padded CIK (e.g., "0000320193"), or company name (e.g., "Moderna").”countrystring“OPTIONAL ISO 3166-1 alpha-2 of the business register you mean ("NO", "FI", "GB", "JP", "FR", "EE", "BR").”
“"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in th…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 3 required
typestringrequired“Entity type.”valuestringrequired“Ticker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193").”sincestringrequired“Window start — ISO date ("2026-04-01") or relative ("7d", "30d", "3m", "1y").”
“"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
claimstringrequired“Natural-language factual claim, e.g., "Apple's FY2024 revenue was $400 billion" or "Microsoft made about $100B in profit last year".”tolerance_pctnumber“Max percent deviation still graded approximately_correct (0.5–50).”
“TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs, 3 required
companystringrequired“Ticker ("AAPL"), 10-digit CIK ("0000320193"), or company name.”attributestringrequired“Which figure.”periodobjectrequired“The reporting period, stated explicitly.”freshnessstring“cached (default) permits an eligible stored answer; fresh requires an upstream refresh and never silently falls back to stale data.”max_agenumber“Maximum age in seconds of the upstream publication, not our fetch.”as_ofstring“Past ISO timestamp with timezone.”restatementstring“Default "as_amended" — the latest filed figure for the period, with everything it superseded listed.”basisstring“Only "consolidated" in v1.”exclude_publishersarray“Publisher ids forbidden for fact retrieval: sec, fmp, alphavantage.”
“Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corpo…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
namestringrequired“The company name as you have it, in its own script.”countrystring“OPTIONAL ISO 3166-1 alpha-2 of the register you mean ("GB", "NO", "FI", "FR", "JP", "EE", "BR").”limitnumber“Maximum candidates to return, 1-50 (default 10).”
“Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependenc…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
packagestringrequired“npm package name.”versionstring“Specific version to check (e.g., "18.3.1").”
“Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 1 required
marketstringrequired“Polymarket slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), full URL ("https://polymarket.com/event/..."), or question text ("Will Bi…”depthstring“quick = 2-3 evidence sources, thorough = full fan-out.”include_rawboolean“Default false.”
“Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
eventstring“Single-event mode (use this if you know the specific Polymarket event): event slug like "fed-decision-may-2026" or "when-will-bitcoin-hit-150k".”topicstring“Cross-event mode (use this if you want to scan related events across the platform): a topic or seed question like "Fed rate decision" or "Strait of Hormuz traf…”
“Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
9 inputs
windowstring“Polymarket volume window to filter markets.”limitnumber“Top N edges to return after ranking.”min_edge_ppnumber“Minimum |edge| in percentage points to include (default 0.5).”slippage_ppnumber“Assumed execution slippage in percentage points per leg (default 0.3), for bid/ask + thin depth cost that a last-trade price does not show.”category_filterstring“Comma-separated list to restrict the output: "model_driven" (crypto_price + news_momentum), "structural_arbitrage" (partition_overround), "concentrated_longsho…”min_kellynumber“Minimum half-Kelly fraction (as decimal, e.g.”min_partition_leg_kellynumber“Minimum BEST per-leg half-Kelly fraction across a partition_overround opportunity's top_legs (or longshot_basket legs).”min_liquiditynumber“Tradeable-edge filter.”max_spread_ppnumber“Tradeable-edge filter.”
“Cross-venue spread between Kalshi and Polymarket for the same resolving question.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs
topicstring“Subject to compare.”kalshi_event_tickerstring“Explicit Kalshi event ticker, e.g.”polymarket_event_slugstring“Explicit Polymarket event slug, e.g.”
“Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/Predicti…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs
marketstring“Single-market mode: market slug or full polymarket.com URL.”eventstring“Basket mode: event slug or full polymarket.com URL — checks every leg of the partition.”sidestring“Single-market: buy_yes | sell_yes | buy_no | sell_no (default buy_yes).”size_usdnumber“Single-market: USD to spend (buys) or target proceeds (sells).”
“Edge persistence and decay telemetry built from daily polymarket_edges snapshots.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
daysnumber“Lookback in days (default 14, clamp 2-30).”windowstring“Which polymarket_edges window family to read snapshots for: 24hr | 1wk | 1mo (default 1wk).”
“Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs
citystring“City to price, e.g.”series_tickerstring“Explicit Kalshi series, e.g.”datestring“Settlement date as YYYY-MM-DD.”market_typestring“"high_temp" (default) | "precip".”backtest_daysnumber“Run measurement mode over the last N settled days (max 60) instead of pricing today.”
“Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market T…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
venuestringrequired“Which venue to fetch the market from.”marketstringrequired“Polymarket (.com or .us) market slug or URL, OR a Kalshi market ticker (preferred) or event ticker (falls back to a representative market under that event).”
“Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares sourc…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 2 required
aobjectrequired“First market to compare.”bobjectrequired“Second market to compare.”
“JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live market…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
hoursnumber“Look-ahead window in hours from now.”categoriesstring“Comma or space separated subset of econ|fed|fda|sec|court, or "all" (default).”
“REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
6 inputs
venuestring“polymarket | polymarket-us | kalshi | all (default polymarket).”assetstring“btc (default) | eth | sol | xrp | bnb.”horizonstring“15m (default).”bucket_ppnumber“Price-bucket width in percentage points: 5 | 10 (default) | 20 | 25 | 50.”minutenumber“Minutes elapsed since window open, 0-based.”side_conventionstring“"favorite" (default) folds each window onto whichever side was the favorite — the frame published claims about early favorites use.”
“What did a web page say on a given date?”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 2 required
urlstringrequired“The page address, e.g.”datestringrequired“The date to look up, as YYYY-MM-DD (e.g.”max_gap_daysnumber“Furthest a capture may be from the date and still be used, in days.”max_charsnumber“Characters of page text to return.”
“What changed on a web page between two dates?”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 3 required
urlstringrequired“The page address, e.g.”date_astringrequired“The earlier date, as YYYY-MM-DD (e.g.”date_bstringrequired“The later date, as YYYY-MM-DD (e.g.”max_gap_daysnumber“Furthest a capture may be from each date and still be used, in days.”
“Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
5 inputs, 3 required
entityobjectrequired“The row/company to research.”questionstringrequired“The question to answer about this company, in natural language, e.g.”output_schemaobjectrequired“JSON Schema object naming the fields to extract, e.g.”sourcesstring“Where to look: "web" (company site only), "catalog" (entity_profile only), "both" (default).”max_costnumber“Cost ceiling in US dollars for this one row.”
“Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
entityobjectrequired“The row/company to classify.”labelsarrayrequired“Candidate labels to test, 2-30 strings, e.g.”textstring“Text to classify directly (a description, a page you already fetched, etc.) — cheapest path, skips any fetch.”
“What other AI agents are calling on Pipeworx right now.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
windowstring“24h (default) | 7d | 30d.”
“What can I ask Pipeworx?”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
topicstring“Optional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news.”
“Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
urlstringrequired“Full URL of the site to summarize, e.g.”max_linksnumber“Maximum number of link entries to include (default 25, max 50).”
“Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
entitystringrequired“The thing to ask about.”contextstring“Optional: a phrase locating the entity (e.g.”modelsarray“Which models to probe.”_apiKeystring“Optional Anthropic API key (sk-ant-...) — only needed if "anthropic" is in models.”
“Compare AI visibility across multiple entities side-by-side.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
4 inputs, 1 required
entitiesarrayrequired“Array of 2-8 entities to compare (brand/business/product names).”contextstring“Optional shared context applied to every probe (e.g.”modelsarray“Which models to probe.”_apiKeystring“Optional Anthropic API key — only if "anthropic" is in models.”
“Tell the Pipeworx team something is broken, missing, or needs to exist.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs
typestring“bug = something broke or returned wrong data.”messagestring“Your feedback in plain text.”contextobject“Optional structured context: which tool, pack, or vertical this relates to.”claim_tokenstring“Read the reply to a report you filed earlier: pass the `pwfb_…` token that filing returned, with no other arguments.”
“Save data the agent will need to reuse later — across this conversation or across sessions.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
9 inputs, 2 required
keystringrequired“Memory key (e.g., "subject_property", "target_ticker", "user_preference").”valuestringrequired“Value to store (any text — findings, addresses, preferences, notes).”namestring“Alias for key.”kstring“Alias for key.”labelstring“Alias for key.”contentstring“Alias for value.”textstring“Alias for value.”datastring“Alias for value.”vstring“Alias for value.”
- recallon 305 other servers
“Retrieve a value previously saved via remember, or list all saved keys (omit the key argument).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
keystring“Memory key to retrieve (omit to list all keys).”namestring“Alias for key.”kstring“Alias for key.”labelstring“Alias for key.”
- forgeton 268 other servers
“Delete a previously stored memory by key.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
4 inputs, 1 required
keystringrequired“Memory key to delete.”namestring“Alias for key.”kstring“Alias for key.”labelstring“Alias for key.”
- ak_statute
“Get the FULL TEXT of a section of the Alaska Statutes (Alaska Code) by citation.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
citationstringrequired“Section citation, title.chapter.section, e.g.”
- ak_search
“Search the Alaska Statutes BY TOPIC or keyword rather than citation — "alcohol license", "murder", "child custody".”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
querystringrequired“Topic or keywords, e.g.”limitnumber“Max results to return, default 10, max 25.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 40 tools
- Says what it returns
- 100% of 40 tools
- States limits, defaults or errors
- 44% of 36 tools
- Says when to use it
- 100% of 40 tools
- Items covered per tool
- 3.5 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 174
- Tools with a description
- 100% of 44
- Typical description length
- 1,441 characters
The tool set
Counted from the listing
- Tools
- 44
- Size of the list
- about 33,146 tokens for an agent to load (characters ÷ 4)
- Naming
- 39 of 44 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 40 of 44 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://gateway.pipeworx.io/alaska-code/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"alaska-code": {
"url": "https://gateway.pipeworx.io/alaska-code/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"alaska-code": {
"type": "http",
"url": "https://gateway.pipeworx.io/alaska-code/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"alaska-code","type":"http","url":"https://gateway.pipeworx.io/alaska-code/mcp"}'Claude Code
claude mcp add --transport http alaska-code https://gateway.pipeworx.io/alaska-code/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://gateway.pipeworx.io/alaska-code/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint gateway.pipeworx.io/alaska-code/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
| Repository github.com/pipeworx-io/mcp-alaska-code | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.pipeworx-io · 1,894 servers
- GitHub owner
- an organization (pipeworx-io)
- Repository
- github.com/pipeworx-io/mcp-alaska-code
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 5 record checks met · 4 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.pipeworx-io/alaska-code
Answered from the data aboveIs io.github.pipeworx-io/alaska-code safe to install?
We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 4 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Is io.github.pipeworx-io/alaska-code free to use?
Its website (pipeworx.io/packs/alaska-code) describes a usage-based pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.
Does io.github.pipeworx-io/alaska-code need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.pipeworx-io/alaska-code been security tested?
Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.
What can io.github.pipeworx-io/alaska-code do?
It lists 44 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete, generate content and do something else. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.pipeworx-io/alaska-code change or delete data?
4 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.pipeworx-io/alaska-code publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Where is the source code of io.github.pipeworx-io/alaska-code?
In github.com/pipeworx-io/mcp-alaska-code, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.pipeworx-io/sports-game-oddsSports Game Oddsalso has tools that creates or changes data, deletes, generates content, does something else, reads or searchescompare with this one
- io.github.pipeworx-io/ted-euTed Eualso has tools that creates or changes data, deletes, generates content, does something else, reads or searchescompare with this one
- com.innergcomplete/shearqueryShearQuery — Barber & Beauty Industry Dataalso has tools that creates or changes data, deletes, generates content, does something else, reads or searchescompare with this one
- io.github.pipeworx-io/42matters42mattersalso has tools that creates or changes data, deletes, generates content, does something else, reads or searchescompare with this one
- io.github.pipeworx-io/511-sf-bay511 Sf Bayalso has tools that creates or changes data, deletes, generates content, does something else, reads or searchescompare with this one
- io.github.pipeworx-io/7timer7timeralso has tools that creates or changes data, deletes, generates content, does something else, reads or searchescompare with this one
Active servers whose topic is also “data-and-databases” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: exercised
- Fake assistant turns: exercised
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
5 exercised11 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 12Hidden content
audience-hidingChecks resources that hide content from the user.exercised - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 125 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 44 tools, 0 resources, 12 prompts.
- 2,545 msFinished: 5 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“free tier 50 calls/day”
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.pipeworx-io/alaska-code: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.pipeworx-io/alaska-code
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.pipeworx-io/alaska-code)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology