MCP servers › io.github.TheOyster › liffey-metals
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.TheOyster/liffey-metals
Ireland's most trusted gold & silver buyer: live prices, payout estimates, free postal pack orders. — the publisher's description
Summary
io.github.TheOyster/liffey-metals is a remote MCP server listed in the official MCP registry at version 1.4.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 13 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Tools
- 13
- Described as changing data
- 1 of 13 toolsAI-classified
- Topic
- finance-and-paymentsAI-classified
- Pricing
- usage-basedAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 1 tool is described as changing something (request_postal_pack): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call it.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.4.0, published 2026-10-16 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, all on 2026-10-16; 2 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 2 versions
1.4.0· 2026-10-161.1.0· 2026-10-16
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.4.0 (published 2026-10-16).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventory1 of 13 tools are described as changing something (creating, editing, deleting, sending or running).
- get_buy_pricereads or searches
“The net price Liffey Metals pays today, in euro per gram of the item, for one metal and carat or fineness, with the spot quote time (spotAsOf), the basis and the deductions in plain English.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
metalstringrequired“Lowercase: gold, silver or platinum”caratnumber or string“Carat, hallmark fineness number or grade word, e.g.”countystring“Optional county, as a slug or name: 'cork', 'County Cork', 'Co.”
- get_buy_pricesreads or searches
“The net prices Liffey Metals pays today, in euro per gram of the item, for 9ct gold, 14ct gold, 18ct gold, 22ct gold, 24ct gold, Gold bullion / sovereigns, Sterling silver (925), Fine silver (999), O…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- estimate_payoutreads or searches
“What we would pay for a given weight of gold, silver or platinum at today's published rate.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 3 required
metalstringrequired“Lowercase: gold, silver or platinum”puritynumber or stringrequired“Carat, hallmark fineness number or grade word, e.g.”weight_gramsnumberrequired“Weight of the item in grams (0 to 100000)”
- get_sell_pricereads or searches
“What Liffey Metals charges today for casting grain, bullion coins and bars, VAT inclusive, in euro per gram or per piece, with the spot quote time for spot-linked products and whether each is in stoc…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
productstring“Optional product slug or words from its name, e.g.”
“Every service Liffey Metals offers with a one-line factual description and its URL: buying gold, silver and platinum, selling by post, refining, XRF testing, valuations, business accounts and the Buy…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
- get_postal_pack_inforeads or searches
“How the free insured postal pack works: how to request it, what it covers in transit and on what condition, the free-return terms if the seller declines, the offer validity, the return postage deduct…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
countystring“Optional county, as a slug or name: 'cork', 'County Cork', 'Co.”
- how_to_sellreads or searches
“The seller's checklist for gold, silver or platinum: weigh it, photograph the hallmark, get the quote, confirm and send.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
metalstringrequired“Lowercase: gold, silver or platinum”
- how_selling_worksreads or searches
“The postal selling process step by step: requesting a free insured pack, posting, XRF testing on camera, the itemised offer, payment by bank transfer, free returns if declined, ID requirements and th…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
“Every county with its country (IE or NI), province, postal model (free insured pack in the Republic of Ireland; the seller's own tracked post to the Dublin PO box from Northern Ireland), the arrangem…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
countrystring“Optional filter: IE for the Republic of Ireland, NI for Northern Ireland”
“The published guides and fact sheets, each with what it answers and its URL: selling gold, 9ct gold, scrap gold value, how buyers price jewellery, XRF testing, hallmarks, sterling versus plate, coins…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
topicstring“Optional words, e.g.”
“Name, founder, contact details (WhatsApp preferred, with the link to hand a person and the reply time), enquiry hours, location and how to deal with us, service area, services, the verifiable trust s…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
“Short, factual answers to the questions people ask before selling gold, silver or jewellery in Ireland: how to compare buyers, what to ask, safety of posting, payment, hallmarks, stones, tax, coins.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
topicstring“Optional keyword, e.g.”
Show 1 more tool
- request_postal_packcreates or changes datadescribed as changing data
“Orders a free insured postal pack for a person at a Republic of Ireland address and returns the Bosca number.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
16 inputs, 11 required
namestringrequired“The person's full name, as it should appear on the pack”address_line1stringrequired“House or apartment and street, or townland”address_line2string“Optional second address line”townstringrequired“Town or city”countystringrequired“County in the Republic of Ireland, e.g.”eircodestringrequired“The person's Eircode, 7 characters, e.g.”emailstringrequired“The person's own email: the receipt, the offer and every update go there”phonestringrequired“Phone number, a mobile preferred, e.g.”metal_typestringrequired“What they are sending: gold, silver or mixed”rough_descriptionstringrequired“A rough description of the items, e.g.”consent_contactbooleanrequired“Must be true: the person agrees to be emailed about the pack and contacted about their items”accepts_termsbooleanrequired“Must be true, and only after the person has agreed to this statement, which you read to them: "I am 18 or over and I own the items I will send, or am authorise…”source_of_itemsstring“Optional: where the items came from, if the person said; defaults to other”estimated_value_eurnumber“Rough total value in euro; ask for it.”item_countinteger“Optional rough number of items”agentstring“Optional: the name of the assistant or model making the request, recorded with the lead”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 13 tools
- Says what it returns
- 100% of 13 tools
- States limits, defaults or errors
- 0% of 4 tools
- Says when to use it
- 0% of 13 tools
- Items covered per tool
- 2.7 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 28
- Tools with a description
- 100% of 13
- Typical description length
- 412 characters
The tool set
Counted from the listing
- Tools
- 13
- Size of the list
- about 3,723 tokens for an agent to load (characters ÷ 4)
- Naming
- 13 of 13 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 13 of 13 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://mcp.liffeymetals.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"liffey-metals": {
"url": "https://mcp.liffeymetals.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"liffey-metals": {
"type": "http",
"url": "https://mcp.liffeymetals.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"liffey-metals","type":"http","url":"https://mcp.liffeymetals.com/mcp"}'Claude Code
claude mcp add --transport http liffey-metals https://mcp.liffeymetals.com/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.liffeymetals.com/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.liffeymetals.com/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.TheOyster/liffey-metals
Answered from the data aboveIs io.github.TheOyster/liffey-metals safe to install?
We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 1 of its tools describes changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Is io.github.TheOyster/liffey-metals free to use?
Its website (liffeymetals.com/) describes a usage-based pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.
Does io.github.TheOyster/liffey-metals need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.TheOyster/liffey-metals been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.
What can io.github.TheOyster/liffey-metals do?
It lists 13 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.TheOyster/liffey-metals change or delete data?
1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.vybenetwork/solana-mcp-vybeSolana MCP by Vybealso has tools that creates or changes data, reads or searchescompare with this one
- io.github.mnemox-ai/tradememory-protocolalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.agent-next/polymarket-paper-traderPolymarket Paper Traderalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.DeHor-Labs/mcp-fiscal-brasilMCP Fiscal Brasilalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.codespar/mcp-khipualso has tools that creates or changes data, reads or searchescompare with this one
- io.github.nirholas/agentcore-payments-mcpthree.ws Agent Paymentsalso has tools that creates or changes data, reads or searchescompare with this one
Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,547 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 13 tools, 0 resources, 0 prompts.
- 4,374 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“We pay per gram Live from the London market”
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.TheOyster/liffey-metals: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.TheOyster/liffey-metals
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.TheOyster/liffey-metals)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology