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.

FxLayer

REMOTE · FXLAYERHQ.COM

Indian FEMA compliance: RBI purpose codes, EDPMS / IDPMS, Form 145 / 146 and export deadlines

Available components

+4 this week 85 Trust /100

Last scanned (6 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 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 Security83
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3288 tokens (~91/item across 36 items; 8 tools + 28 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 27 Oct 26 +1

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

  • 26 Oct 26 0
    • Tool “export_realisation_deadline” rewrote its description, which is the text the model reads security
  • 25 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.

  • 23 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.

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 5 Nov 2026 · Probed https://fxlayerhq.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fxlayerhq.com CN=WR3,O=Google Trust Services,C=US 25 Oct 2026 23 Jan 2027 RSA 2048 SHA256-RSA b8fd98a2d3cd2b310a12c91dd73ae487
SANs: fxlayerhq.com, www.fxlayerhq.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 1 Sept 1998 28 Jan 2028 RSA 2048 SHA1-RSA 40000000001154b5ac394

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of fxlayerhq.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
fxlayerhq.com. present 17658, 21945 13, 13 Verified
fxlayerhq.com. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://cdnjs.cloudflare.com/ajax/libs/jszip/3.10.1/jszip.min.js https://checkout.razorpay.com; style-src 'self' 'unsafe-inline'; font-src 'self' data:; img-src 'self' data: blob: https://cdn.razorpay.com; connect-src 'self' https://api.razorpay.com https://lumberjack.razorpay.com https://localhost.emudhra.com:26769; frame-src 'self' blob: data: https://api.razorpay.com https://checkout.razorpay.com https://www.youtube-nocookie.com; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fxlayerhq.com/mcp Verified 200
http (plaintext) http://fxlayerhq.com/mcp HTTPS enforced 301 https://fxlayerhq.com/mcp
MCP tools · 8 exposed · ~577 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
about_fxlayer ~31

What FxLayer is, its modules, plans with starting prices, and where to sign up or read more.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

export_realisation_deadline ~109

The last day to realise and repatriate an export's proceeds under FEMA (for exports from 1 October 2026, nine months from the date of export, or twelve when invoiced or settled in rupees), with the rule and its source.

NameTypeReqDescription
currencystring–Invoice currency, e.g. USD or INR.
export_datestringyesShipping Bill date (goods) or invoice date (services), YYYY-MM-DD.
kindstring––

No output schema declared.

No examples provided.

fetch ~55

The full text (Markdown) of a guide or a purpose-code page, by the id `search` returned (guide:<slug>, code:<code>) or by its address on fxlayerhq.com.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

find_purpose_codes ~114

RBI purpose codes that fit a payment or receipt described in plain words, best first, each with its bank form (Form A1 / A2), Form 145 / 146, income-tax nature, GST and reporting.

NameTypeReqDescription
directionstring–inward = money received from abroad (P codes), outward = money paid abroad (S codes), any = both.
limitinteger––
querystringyesWhat the money is for, e.g. 'software development for a US client'.

No output schema declared.

No examples provided.

get_purpose_code ~78

One RBI purpose code (e.g. P0802, S1006) with the reasoning: which bank form, income-tax nature and Form 145 / 146 part, GST, reporting, cautions and the matching code for the other direction.

NameTypeReqDescription
codestringyese.g. P0802 or S0802

No output schema declared.

No examples provided.

regulatory_updates ~62

The RBI / FEMA / income-tax / GST changes FxLayer follows: the rule, when it takes effect, its source and what changed in FxLayer. Newest first.

NameTypeReqDescription
limitinteger––
querystring–Optional words to filter by.

No output schema declared.

No examples provided.

search ~65

Search FxLayer's compliance guides and the RBI purpose-code reference with plain words (for example 'EDPMS entry not closed', 'Form 145 Part C', 'software export purpose code'). Returns ids for `fetch`.

NameTypeReqDescription
querystringyesPlain words or a purpose code.

No output schema declared.

No examples provided.

services_edf_due_date ~63

When the monthly EDF for a services export invoice is due (30 days from the end of the month of invoicing, for invoices from 1 October 2026), with the rule and its source.

NameTypeReqDescription
invoice_datestringyesYYYY-MM-DD

No output schema declared.

No examples provided.

Install

How do I install the FxLayer MCP server?

FxLayer is a hosted endpoint at https://fxlayerhq.com/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 · fxlayerhq.com

# add to Claude Code
claude mcp add --transport http com-fxlayerhq-fxlayer 'https://fxlayerhq.com/mcp'
Common questions

What is the FxLayer MCP server?

FxLayer is an MCP server listed in the public MCP registry as com.fxlayerhq/fxlayer. Indian FEMA compliance: RBI purpose codes, EDPMS / IDPMS, Form 145 / 146 and export deadlines. This page covers its hosted endpoint (https://fxlayerhq.com/mcp).

Is the FxLayer MCP server safe to use?

FxLayer scores 85 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 FxLayer MCP server expose?

FxLayer exposes 8 tools: search, fetch, find_purpose_codes, get_purpose_code, export_realisation_deadline, and 3 more. Their descriptions and schemas cost roughly 577 tokens of context every time the server is loaded.

Does the FxLayer MCP server require authentication?

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

Is the FxLayer MCP server still maintained?

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