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.

SocialForex

REMOTE · TOOLFOREX.XYZ

Live forex, gold & crypto quotes, economic calendar, screener, currency strength, lot-size calc

Available components

−51 this week 18 Trust /100

Last scanned (18 hours ago)

Scores higher than 4% of remote servers

Reachable. Last reached 4 Nov 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 Security46
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 4 Nov 26 −53
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: partial → unverified ▼ security
    • Stability: 0.33 → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 1 Nov 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.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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.

  • 28 Oct 26 +51
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • HSTS header: fail → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.13 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 27 Oct 26 −50
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.07 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • HSTS header: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 26 Oct 26 +1

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

  • 25 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 24 Oct 26 67

    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 4 Nov 2026 · Probed https://toolforex.xyz/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=toolforex.xyz CN=YE1,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA384 602dc32d56c30fd91ba6c87ea9a415eef5b
SANs: *.toolforex.xyz, toolforex.xyz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of toolforex.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
toolforex.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 530
Header Value
x-frame-options SAMEORIGIN
referrer-policy same-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://toolforex.xyz/api/mcp HTTP error 530
http (plaintext) http://toolforex.xyz/api/mcp Inconclusive 530
MCP tools · 6 exposed · ~412 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
calculate_position_size ~119

Lot size so that hitting the stop loss loses `riskPct` % of the balance. Account currency is assumed to be USD.

NameTypeReqDescription
balancenumberyesAccount balance in USD
entrynumberyes–
leveragenumber–e.g. 500 for 1:500 — adds required margin
riskPctnumberyesRisk per trade in %, e.g. 1
stopLossnumberyes–
symbolstringyese.g. EURUSD, XAUUSD, USDJPY

No output schema declared.

No examples provided.

get_currency_strength ~31

Relative strength of the 8 major currencies, derived from today's % change across available pairs. Sorted strongest first.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_economic_calendar ~88

Upcoming (and optionally recent) macro events with impact, forecast, previous and actual values. Times are UTC.

NameTypeReqDescription
currenciesarray–ISO currency codes, e.g. ["USD", "EUR"]. Omit for all.
hoursAheadnumber––
hoursBacknumber–Include events released in the last N hours.
minImpactstring––

No output schema declared.

No examples provided.

get_market_sessions ~33

Whether the forex market is open, active sessions (Sydney/Tokyo/London/New York), current and upcoming overlaps.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_quotes ~57

Current bid/ask and daily % change for forex majors/minors, gold, silver, oil and crypto.

NameTypeReqDescription
symbolsarray–Symbols without slash, e.g. ["EURUSD", "XAUUSD"]. Omit for all.

No output schema declared.

No examples provided.

get_screener ~84

Per-symbol technicals: TradingView recommendation per timeframe (M15/H1/H4/D1, -1 strong sell … +1 strong buy), RSI, ADX, MACD, Bollinger position, stochastic state and ATR.

NameTypeReqDescription
symbolsarray–Symbols without slash, e.g. ["EURUSD", "XAUUSD"]. Omit for all.

No output schema declared.

No examples provided.

Install

How do I install the SocialForex MCP server?

SocialForex is a hosted endpoint at https://toolforex.xyz/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 · toolforex.xyz

# add to Claude Code
claude mcp add --transport http namlxuit056-social-forex 'https://toolforex.xyz/api/mcp'
Common questions

What is the SocialForex MCP server?

SocialForex is an MCP server listed in the public MCP registry as io.github.namlxuit056/social-forex. Live forex, gold & crypto quotes, economic calendar, screener, currency strength, lot-size calc. This page covers its hosted endpoint (https://toolforex.xyz/api/mcp).

Is the SocialForex MCP server safe to use?

SocialForex scores 18 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 SocialForex MCP server expose?

SocialForex exposes 6 tools: get_quotes, get_economic_calendar, get_screener, get_currency_strength, get_market_sessions, calculate_position_size. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.

Does the SocialForex MCP server require authentication?

Its publisher declares no required credentials for SocialForex. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the SocialForex MCP server still maintained?

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