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.

FocusPulse

REMOTE · MCP.FOCUSPULSE.PRO

India and US news stories linked to listed companies, commodities and indices, with sources.

+4 this week 79 Trust /100

Last scanned (6 hours ago)

Scores higher than 82% of remote servers

Reachable. Last reached 17 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 Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 691 tokens (~172/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 17 Oct 26 +1
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Stability: unverified → 0.37 ▲ functional
  • 16 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.30 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 15 Oct 26 +1

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

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 +1
    • Schema quality: 217 → 172 ▲ functional
  • 7 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 6 Oct 26 74

    First indexed and scored.

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 17 Oct 2026 · Probed https://mcp.focuspulse.pro/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.focuspulse.pro CN=YR1,O=Let's Encrypt,C=US 5 Oct 2026 3 Jan 2027 RSA 2048 SHA256-RSA 6ec278351af16f682cb9abb237ff64126ec
SANs: mcp.focuspulse.pro
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 mcp.focuspulse.pro. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
pro. present 33289, 42154 8, 8 Verified
focuspulse.pro. 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
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://checkout.razorpay.com https://telegram.org https://challenges.cloudflare.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self' data:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://checkout.razorpay.com https://lumberjack.razorpay.com https://www.google-analytics.com; frame-src 'self' https://oauth.telegram.org https://challenges.cloudflare.com https://api.razorpay.com https://checkout.razorpay.com;
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.focuspulse.pro/mcp Verified 200
http (plaintext) http://mcp.focuspulse.pro/mcp HTTPS enforced 308 https://mcp.focuspulse.pro/mcp
MCP tools · 4 exposed · ~691 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
get_instrument_stories ~248

News stories linked to one instrument, newest first, for one country (IN or US). The instrument can be a listed company by name or ticker ('Reliance', 'HDFCBANK'), a commodity ('crude oil', 'gold'), an index ('Nifty'), the rupee, or a central bank's policy rate ('repo rate'). Unlike search_stories, which matches words, this returns the stories linked to that instrument. A name FocusPulse does not track returns UNKNOWN_INSTRUMENT — use list_instruments to see what is covered. Stories are kept 48 hours. Information only — never investment advice.

NameTypeReqDescription
countrystringyesMarket the story affects: 'IN' (India) or 'US'.
cursorstring–next_cursor from the previous page of the same request. Omit for the first page.
hoursinteger–Lookback window in hours, default 48, max 48.
instrumentstringyesOne company (name or NSE/US ticker), commodity, index, 'rupee' or 'repo rate'.
limitinteger–Stories per page, default 5, max 10.
NameTypeReqDescription
codestringyes–
countrystringyes–
instrumentsarrayyes–
next_cursorstring|nullyes–
storiesarrayyes–
totalnumberyes–
window_hoursnumberyes–

No examples provided.

get_story ~105

One story by its id, as returned by search_stories or get_instrument_stories: the headline, a summary, what it reports about the instruments it is linked to, the publications that reported it (up to 10, with links) and earlier stories on the same instruments. Returns NOT_FOUND for an unknown id or a story older than 48 hours. Information only — never investment advice.

NameTypeReqDescription
idstringyesThe story's id, from a previous result.
NameTypeReqDescription
codestringyes–
earlierarrayyes–
story–yes–

No examples provided.

list_instruments ~121

The listed companies, commodities, indices, currency and central-bank policy rates that have at least one FocusPulse story right now, for one country (IN or US), with how many stories each has. Use it to see what is covered before asking for an instrument's stories with get_instrument_stories. Information only — never investment advice.

NameTypeReqDescription
countrystringyesMarket: 'IN' (India) or 'US'.
hoursinteger–Lookback window in hours, default 24, max 48 — older stories are purged.
NameTypeReqDescription
codestringyes–
countrystringyes–
instrumentsarrayyes–
totalnumberyes–
window_hoursnumberyes–

No examples provided.

search_stories ~217

News stories from the last 48 hours for one country (IN or US) that are linked to a listed company, commodity, index or the rupee. Each story says what it reports about those instruments and names up to three sources. Information only — never investment advice. Without a query it returns the most relevant stories; with one, the stories that mention the query's words. Results are paged with a cursor.

NameTypeReqDescription
countrystringyesMarket the story affects: 'IN' (India) or 'US'.
cursorstring–next_cursor from the previous page of the same search. Omit for the first page.
hoursinteger–Lookback window in hours, default 24, max 48 — older stories are purged.
limitinteger–Stories per page, default 5, max 10.
querystring–Words to look for, e.g. a company, commodity or topic: 'crude oil', 'Reliance', 'RBI'.
NameTypeReqDescription
codestringyes–
countrystringyes–
next_cursorstring|nullyes–
storiesarrayyes–
totalnumberyes–
window_hoursnumberyes–

No examples provided.

Install

How do I install the FocusPulse MCP server?

FocusPulse is a hosted endpoint at https://mcp.focuspulse.pro/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 · mcp.focuspulse.pro

# add to Claude Code
claude mcp add --transport http pro-focuspulse-focuspulse 'https://mcp.focuspulse.pro/mcp'
Common questions

What is the FocusPulse MCP server?

FocusPulse is an MCP server listed in the public MCP registry as pro.focuspulse/focuspulse. India and US news stories linked to listed companies, commodities and indices, with sources. This page covers its hosted endpoint (https://mcp.focuspulse.pro/mcp).

Is the FocusPulse MCP server safe to use?

FocusPulse scores 79 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 FocusPulse MCP server expose?

FocusPulse exposes 4 tools: search_stories, list_instruments, get_instrument_stories, get_story. Their descriptions and schemas cost roughly 691 tokens of context every time the server is loaded.

Does the FocusPulse MCP server require authentication?

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

Is the FocusPulse MCP server still maintained?

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