Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Liffey Metals is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Ireland's most trusted gold & silver buyer: live prices, payout estimates, free postal pack orders.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http liffey-metals-mcp https://mcp.liffeymetals.com/mcp
# 2 — ask your agent for something these tools do
# get_buy_price, get_buy_prices, estimate_payout and 10 more
Liffey Metals costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
THAll 1 server
TheOyster1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http liffey-metals-mcp https://mcp.liffeymetals.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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. Give the seller's county to add that county's postal arrangement and page. Omit carat for every grade of the metal. Same figures as https://liffeymetals.com/prices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metal | string | yes | Lowercase: gold, silver or platinum |
| carat | no | Carat, hallmark fineness number or grade word, e.g. 9, '18ct', 750, 'sterling', 925. Omit for every grade of the metal. | |
| county | string | no | Optional county, as a slug or name: 'cork', 'County Cork', 'Co. Antrim'. Adds that county's postal arrangement and page. |
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), Other silver (800 to 900), Sterling-handled knives (925), Other silver-handled knives (800 to 900), Platinum (950), with the spot quote time. Same figures as https://liffeymetals.com/prices. No fees are
No parameter schema on file.
What we would pay for a given weight of gold, silver or platinum at today's published rate. purity accepts carats (9, 14, 18, 22, 24, '18ct', '18k'), hallmark numbers (375, 585, 750, 916, 999, 925, 958, 800) or words (sterling, fine, bullion). Weight is grams of the item as it sits on the scale. Returns the rate per gram, the total and the spot quote time; the final figure follows weighing and XRF
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metal | string | yes | Lowercase: gold, silver or platinum |
| purity | yes | Carat, hallmark fineness number or grade word, e.g. 9, '18ct', 750, 'sterling' | |
| weight_grams | number | yes | Weight of the item in grams (0 to 100000) |
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 stock. Give a product slug or words from its name for one product; omit for every product. Same figures as https://liffeymetals.com/shop.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | no | Optional product slug or words from its name, e.g. 'casting grain', '9ct grain', 'sovereign', 'silver bar'. Omit for every product. |
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 Buyer Programme. Unlisted services are live pages that are not in the navigation.
No parameter schema on file.
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 deduction and when it is waived, payment and ID. Give a county for that county's arrangement (free insured pack in the Republic; own tracked post to Dublin from Northern Ireland).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| county | string | no | Optional county, as a slug or name: 'cork', 'County Cork', 'Co. Antrim'. Adds that county's postal arrangement and page. |
The seller's checklist for gold, silver or platinum: weigh it, photograph the hallmark, get the quote, confirm and send. Each step says what to do and what to look for with that metal, followed by the postal process and the guide to read.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metal | string | yes | Lowercase: gold, silver or platinum |
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 the return postage rule.
No parameter schema on file.
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 arrangement in one sentence and the county page URL, plus the other 26 EU member states we buy from on the Northern Ireland arrangement (WhatsApp quote, then the seller's own insured post to Dublin, no customs
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | 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, tax, inherited jewellery, refining. Optional topic words filter the list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Optional words, e.g. 'hallmarks', 'tax', 'silver plate', 'coins' |
Name, founder, contact details, location and how to deal with us, service area, services, the verifiable trust signals (each with where to check it), the pages to cite and the live Google rating once the listing has reviews (null until then; never a made-up figure).
No parameter schema on file.
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. Optional topic filter matches words in the question.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Optional keyword, e.g. 'post', 'tax', 'coins' |
Orders a free insured postal pack for a person at a Republic of Ireland address and returns the Bosca number. This is the real order: the request is created when you call it, and for gold lots within the postal limits the pack is posted to the address given with no further step from the person. Silver, mixed lots, bullion and lots over 2,000 euro are registered and arranged on WhatsApp instead; th
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The person's full name, as it should appear on the pack |
| address_line1 | string | yes | House or apartment and street, or townland |
| address_line2 | string | no | Optional second address line |
| town | string | yes | Town or city |
| county | string | yes | County in the Republic of Ireland, e.g. Cork, Mayo, Dublin (Northern Ireland addresses are refused with the alternative) |
| eircode | string | yes | The person's Eircode, 7 characters, e.g. D02 X285 (finder.eircode.ie) |
| string | yes | The person's own email: the receipt, the offer and every update go there | |
| phone | string | yes | Phone number, a mobile preferred, e.g. 087 123 4567 or +353 87 123 4567 |
| metal_type | string | yes | What they are sending: gold, silver or mixed |
| rough_description | string | yes | A rough description of the items, e.g. 'two 9ct rings and a broken 18ct chain, about 12 g' |
| consent_contact | boolean | yes | Must be true: the person agrees to be emailed about the pack and contacted about their items |
| accepts_terms | boolean | yes | 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 authorised to sell them. I accept the Liffey Metal |
| source_of_items | string | no | Optional: where the items came from, if the person said; defaults to other |
| estimated_value_eur | number | no | Rough total value in euro; ask for it. It sets the value band on the request and the route: gold up to 2,000 euro goes straight to a pack, lots over 2,000 euro are arranged on WhatsApp, and under 300 |
| item_count | integer | no | Optional rough number of items |
| agent | string | no | Optional: the name of the assistant or model making the request, recorded with the lead |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Liffey Metals or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.4.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestce7dbbad96a7214f2c7ef0a36c1ea8dc8b84416f22ee0a6fd165eaf9034ecbe3
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_buy_price | no tags | |
| get_buy_prices | no tags | |
| estimate_payout | no tags | |
| get_sell_price | no tags | |
| list_services | no tags | |
| get_postal_pack_info | no tags | |
| how_to_sell | no tags | |
| how_selling_works | no tags | |
| list_counties | no tags | |
| get_guides | no tags | |
| get_business_info | no tags | |
| get_faq | no tags | |
| request_postal_pack | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestce7dbbad96a7214f
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.4.0.
1.4.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Liffey Metals can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.