Align
REMOTE · ALIGNLABS.DEV
Cross-border payment lookups: USDT/USDC rates, off-ramp plans, network fees, IBAN checks, holidays
Available components
Last scanned (18 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1074 tokens (~134/item across 8 items; 8 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% 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 9 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 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.
- 19 Nov 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.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 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.
- 15 Nov 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.
- 14 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “plan_offramp” rewrote its description, which is the text the model reads security
- Schema quality: 928 → 1074 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “align_facts” functional
- 13 Nov 26 72
First indexed and scored.
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 21 Nov 2026 · Probed https://alignlabs.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alignlabs.dev | CN=YE1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5d84363e0583a4513a1c0c11fb8c178a267 |
| SANs: *.alignlabs.dev, alignlabs.dev | ||||||
| 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 alignlabs.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| alignlabs.dev. | No DS | 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=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://alignlabs.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://alignlabs.dev/api/mcp | HTTPS enforced | 301 | https://alignlabs.dev/api/mcp |
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 →
align_facts Align's published facts ~97
What Align publishes about itself, each row with the alignlabs.dev page it comes from: the company and its FINTRAC registration, the four account currencies and their rails, the stablecoins and networks accepted, conversion and the OTC desk, rail timings, who can open an account, how pricing works (by quote, no fees listed) and AlignConnect. Optionally return one section.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Only this section |
No output schema declared.
No examples provided.
check_iban Check an IBAN ~96
Validate an IBAN's country code, length, format and check digits for any of the 89 IBAN countries, and name the bank behind its bank code (name, BIC, head office) where the directory has it. A valid IBAN doesn't prove the account exists or belongs to the payee; confirm the account holder's name before paying.
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | yes | The IBAN, with or without spaces |
No output schema declared.
No examples provided.
mica_stablecoin_register MiCA e-money token register ~85
Issuers of e-money tokens (EU-authorized stablecoins such as EURC and USDC) on ESMA's interim MiCA register: legal and commercial name, home member state, supervisor, type of institution and white papers. Optionally filter by name.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Part of an issuer's legal or commercial name, e.g. Circle |
No output schema declared.
No examples provided.
payment_holidays Payment rail holidays ~74
Weekday closures in 2027 for US rails (Fedwire and FedACH, Federal Reserve holidays), euro rails (TARGET/T2 closing days) and UK rails (CHAPS and Bacs, England and Wales bank holidays), with what keeps running and the official sources.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | Only this calendar |
No output schema declared.
No examples provided.
plan_offramp Plan a stablecoin off-ramp ~249
Plan turning USDT or USDC into USD, EUR, GBP or AED in a company bank account: the indicative market value of the amount, the network fee to move the tokens now, each payout rail for that currency with the date the money should arrive if sent now (weekends and holidays included), the rules to check in that currency, a checklist before the first withdrawal, and the next step (a link to ask Align for a quote, plus a sign-up link where Align's convert page for the pair offers one). Indicative information, not a quote or an offer.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | Amount of the token to convert (optional) |
| beforeCutoff | boolean | – | Whether the payout leaves before the bank's cut-off that day (default true) |
| currency | string | yes | Currency the bank account receives |
| network | string | – | Network the tokens are on, e.g. tron, ethereum, solana, base (optional) |
| sendDate | string | – | Day the conversion is made, YYYY-MM-DD between 2026-11-01 and 2027-12-31 (default today, UTC) |
| token | string | yes | – |
No output schema declared.
No examples provided.
search_guides Search Align's guides ~138
Find Align's sourced guides on cross-border business payments: SWIFT, SEPA, ACH, Fedwire and UK rails, business accounts for non-resident companies, stablecoins (USDT, USDC, EURC), and rules such as MiCA, the GENIUS Act, the Travel Rule and DAC8. Returns each guide's answer in two sentences and a markdown version to read in full.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many guides to return, 1 to 10 (default 5) |
| query | string | yes | What you want to know, e.g. 'how long does a SEPA transfer take' |
No output schema declared.
No examples provided.
stablecoin_network_fees Stablecoin network fees ~116
What one USDT or USDC transfer costs in network fees right now, in USD and the network's own token, on Tron, Ethereum, Solana, Base, Arbitrum, Polygon, Optimism, Avalanche and Aptos, with typical time to finality. Refreshed every 10 minutes. Network fees only, not any provider's pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Only this network, e.g. tron, ethereum, solana, base |
| token | string | – | Only this token |
No output schema declared.
No examples provided.
stablecoin_rate Stablecoin to currency rate ~84
Today's indicative market rate for USDT or USDC in USD, EUR, GBP or AED: Kraken's last trade for USD, EUR and GBP, and the USD rate times the UAE central bank's 3.6725 peg for AED. Market prices, not a quote from Align or anyone else.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| token | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Align MCP server?
Align is a hosted endpoint at https://alignlabs.dev/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 · alignlabs.dev
claude mcp add --transport http dev-alignlabs-align 'https://alignlabs.dev/api/mcp'
What is the Align MCP server?
Align is an MCP server listed in the public MCP registry as dev.alignlabs/align. Cross-border payment lookups: USDT/USDC rates, off-ramp plans, network fees, IBAN checks, holidays. This page covers its hosted endpoint (https://alignlabs.dev/api/mcp).
Is the Align MCP server safe to use?
Align scores 76 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 Align MCP server expose?
Align exposes 8 tools: stablecoin_network_fees, check_iban, payment_holidays, mica_stablecoin_register, stablecoin_rate, and 3 more. Their descriptions and schemas cost roughly 939 tokens of context every time the server is loaded.
Does the Align MCP server require authentication?
No. We connected to Align without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Align MCP server still maintained?
Align is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Align MCP server?
VerifyMCP ran 13 checks on Align, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.