Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SwiftPrism

REMOTE · SWIFTPRISM.APP

Plans, prices, and a free trial for US stock and world economic news. Not advice.

Available components

+3 this week 82 Trust /100

Last scanned (22 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 24 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 336 tokens (~67/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Oct 26 0
    • Tool “get_features” rewrote its description, which is the text the model reads security
    • Tool “get_languages” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +2

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 24 Oct 2026 · Probed https://swiftprism.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=swiftprism.app CN=YR1,O=Let's Encrypt,C=US 2 Sept 2026 1 Dec 2026 RSA 2048 SHA256-RSA 5adf6b9505cd08712d890f03c691a15af8d
SANs: swiftprism.app
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of swiftprism.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
swiftprism.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://swiftprism.app/api/mcp Verified 200
http (plaintext) http://swiftprism.app/api/mcp HTTPS enforced 308 https://swiftprism.app/api/mcp
MCP tools · 5 exposed · ~271 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_checkout_link ~71

Returns the link where a person pays for Elite (monthly or yearly). Payment happens on a Stripe page (card, Apple Pay, or Link) after the person signs in. Agents never enter card details. Most people should start with start_trial instead.

NameTypeReqDescription
intervalstring–Billing interval. Default month.

No output schema declared.

No examples provided.

get_features ~51

What Elite and Free include: real-time US stock and world economic headlines, studio Headline Voice, Market Momentum, Deep Insights™, Economic Calendar, holdings, reading languages. Also what SwiftPrism does not do.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_languages ~35

Languages a SwiftPrism Elite member can read headlines, Deep Insights™, and the Economic Calendar in, and hear Headline Voice in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_plans ~41

Current SwiftPrism plans and prices by country (one paid plan, Elite, plus Free), and the free trial terms. Generated from the live price catalog.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

start_trial ~73

Returns the link a person opens to start the free Elite trial. The person creates the account and accepts the Terms themselves. No card is needed. This tool does not create an account or send email.

NameTypeReqDescription
reading_languagestring–Optional. The language the person wants to read in (English, Japanese, or Thai).

No output schema declared.

No examples provided.

Install

How do I install the SwiftPrism MCP server?

SwiftPrism is a hosted endpoint at https://swiftprism.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · swiftprism.app

# add to Claude Code
claude mcp add --transport http app-swiftprism-swiftprism 'https://swiftprism.app/api/mcp'
Common questions

What is the SwiftPrism MCP server?

SwiftPrism is an MCP server listed in the public MCP registry as app.swiftprism/swiftprism. Plans, prices, and a free trial for US stock and world economic news. Not advice. This page covers its hosted endpoint (https://swiftprism.app/api/mcp).

Is the SwiftPrism MCP server safe to use?

SwiftPrism scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SwiftPrism MCP server expose?

SwiftPrism exposes 5 tools: get_plans, get_features, get_languages, start_trial, create_checkout_link. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.

Does the SwiftPrism MCP server require authentication?

No. We connected to SwiftPrism without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SwiftPrism MCP server still maintained?

SwiftPrism is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.