@polyrama/mcp

MCPcommunity

v1.0.1io.github.PolyramaUnknownUpdated 1mo agonpm GitHub

Research Polymarket and Kalshi markets, traders, signals, backtests, and paper orders.

Works in

ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Package

Authorio.github.Polyrama

LicenseUnknown

Version1.0.1

Sourcenpm+mcp-registry

npm@polyrama/mcp

GitHubPolyrama/mcp

SBOMCycloneDX 1.6 ↓

Trust Status

B

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/20

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/5

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—npm Trusted Publishing (Sigstore)+0/5

→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo

—npm maintainer match+0/5

→ Earned once your identity is verified above and that login is an npm maintainer of this package

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface10 tools · none privileged

Security scan✓ Cleanv1.0.1 · 1mo agoHow well does this scan work?

EvalsNone

IndexedAug 19, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

10 tools · none privileged

Statically extracted from the published packagev1.0.1 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

Filter toolsPrivileged only

polyrama_search_marketsSearch live prediction markets tracked by Polyrama across Polymarket and Kalshi. Filter by text or YES probability and sort by volume, movement, spread, or price.

Search live prediction markets tracked by Polyrama across Polymarket and Kalshi. Filter by text or YES probability and sort by volume, movement, spread, or price.

No input schema was published for this tool.

polyrama_get_marketGet live odds, spread, volume, metadata, and history fields for one market by token id.

Get live odds, spread, volume, metadata, and history fields for one market by token id.

No input schema was published for this tool.

polyrama_top_tradersGet the Polymarket wallet leaderboard with portfolio, P&L, volume, activity, and search filters.

Get the Polymarket wallet leaderboard with portfolio, P&L, volume, activity, and search filters.

No input schema was published for this tool.

polyrama_get_traderGet one public Polymarket wallet's portfolio, positions, activity, history, and performance stats.

Get one public Polymarket wallet's portfolio, positions, activity, history, and performance stats.

No input schema was published for this tool.

polyrama_refresh_traderRefresh one public Polymarket wallet's positions and net worth. Requires a token with write:paper scope.

Refresh one public Polymarket wallet's positions and net worth. Requires a token with write:paper scope.

No input schema was published for this tool.

polyrama_recent_signalsGet recent whale prints, volume spikes, price jolts, liquidity, wash-like trade, and market-mispricing signals.

Get recent whale prints, volume spikes, price jolts, liquidity, wash-like trade, and market-mispricing signals.

No input schema was published for this tool.

polyrama_list_botsList the authenticated account's configured Polyrama bots and their current status.

List the authenticated account's configured Polyrama bots and their current status.

No input schema was published for this tool.

polyrama_state_snapshotGet the full current Polyrama dashboard state, including quotes, positions, P&L, signals, wallets, and scanners.

Get the full current Polyrama dashboard state, including quotes, positions, P&L, signals, wallets, and scanners.

No input schema was published for this tool.

polyrama_run_backtestRun a Polyrama strategy against historical market data and return summary statistics, P&L series, and fills. Requires write:paper scope.

Run a Polyrama strategy against historical market data and return summary statistics, P&L series, and fills. Requires write:paper scope.

No input schema was published for this tool.

polyrama_place_paper_orderRecord a paper-only trade in Polyrama. This tool never submits a live order. Requires write:paper scope.

Record a paper-only trade in Polyrama. This tool never submits a live order. Requires write:paper scope.

No input schema was published for this tool.

10 of 10 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Research Polymarket and Kalshi markets, traders, signals, backtests, and paper orders.

Keywords

mcp

Alternatives

Comparing tool surfaces…

Tools exposed

10 tools · none privileged · observed 2026-09-01 by static extraction. A tool surface is what one scan read on one day, not a live capability list.

polyrama_search_markets
polyrama_get_market
polyrama_top_traders
polyrama_get_trader
polyrama_refresh_trader
polyrama_recent_signals
polyrama_list_bots
polyrama_state_snapshot
polyrama_run_backtest
polyrama_place_paper_order

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-01 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

zod4.5.4
@modelcontextprotocol/sdk1.30.017 dependencies
- ajv8.20.04 dependencies
  - fast-deep-equal3.1.3
  - fast-uri3.1.6
  - json-schema-traverse1.0.0
  - require-from-string2.0.2
- zod4.5.4shown above
- cors2.8.62 dependencies
  - object-assign4.1.1
  - vary1.1.2
- hono4.13.5
- jose6.2.10
- express5.2.1+26 not drawn2 dependencies
  - vary1.1.2shown above
  - content-type1.0.5
- raw-body3.0.2+4 not drawn
- ajv-formats3.0.11 dependency
  - ajv8.20.0shown above
- cross-spawn7.0.6+3 not drawn
- eventsource3.0.71 dependency
  - eventsource-parser3.1.1
- content-type1.0.5shown above
- pkce-challenge5.0.1
- @hono/node-server2.1.1
- json-schema-typed8.0.2
- eventsource-parser3.1.1shown above
- express-rate-limit8.7.0+2 not drawn
- zod-to-json-schema3.25.2

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

package cap reached: 48
below the depth cap: 5

http-errors ^2.0.1 — required by send@1.2.1package cap reached
mime-types ^3.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by send@1.2.1package cap reached
on-finished ^2.4.1 — required by send@1.2.1package cap reached
range-parser ^1.2.1 — required by send@1.2.1package cap reached
statuses ^2.0.2 — required by send@1.2.1package cap reached
ms ^2.1.3 — required by debug@4.4.3package cap reached
debug ^4.4.0 — required by router@2.2.0package cap reached
depd ^2.0.0 — required by router@2.2.0package cap reached
is-promise ^4.0.0 — required by router@2.2.0package cap reached
parseurl ^1.3.3 — required by router@2.2.0package cap reached
path-to-regexp ^8.0.0 — required by router@2.2.0package cap reached

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.