Janus Pay for agents: take payments that settle in BSV, refund them, and pay x402 paywalls.
Nothing to run from here
amego MCP by usefulapi 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.
96/100
tool-list score
13
tools declared
remote
at its publisher
—
calls last 7d
What it does
Look up invoices, allowances and number ranges, and check government upload status in amego.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http amego-mcp-by-usefulapi https://amego.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# amego_query_invoice, amego_list_invoices, amego_get_invoice_upload_status and 10 more
amego MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 664 servers
usefulapi664 servers
25 categories
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 amego-mcp-by-usefulapi https://amego.usefulapi.io/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.
Look up one invoice by its invoice number, or by the order number it was issued for. Finds invoices dated within the last 180 days. amego: POST /json/invoice_query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| by | string | yes | invoice = look up by invoice number; order = look up by order number. |
| value | string | yes | The invoice number (at most 10 characters) or the order number (at most 40 characters). |
List the invoices of the company in a date range, one page at a time (headers only: number, dates, buyer, amounts, status). amego: POST /json/invoice_list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_select | yes | Which date to filter on: 1 = invoice date, 2 = creation date. | |
| date_start | string | yes | Date as YYYYMMDD, for example 20241031. |
| date_end | string | yes | Date as YYYYMMDD, for example 20241031. |
| limit | integer | no | Rows per page, 20 to 500 (default 20). |
| page | integer | no | Page number (default 1). |
Check whether the government has accepted each invoice number: the upload status, invoice type, status and total amount. Up to 50 numbers per call. amego: POST /json/invoice_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_numbers | array | yes | Invoice numbers to check, up to 50. |
Get a link to the PDF of one invoice (valid for 10 minutes). A carrier invoice can be downloaded only after it wins a prize. amego: POST /json/invoice_file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| by | string | yes | invoice = look up by invoice number; order = look up by order number. |
| value | string | yes | The invoice number (at most 10 characters) or the order number (at most 40 characters). |
| download_style | no | PDF layout. 0 = A4 full page (default for invoices with a buyer tax ID), 1 = A4 with address and A5, 2 = A4 with two A5, 3 = A5, 5 = QR code A4. |
List the company's invoices that won a prize in one two-month period. amego advises asking on the 1st day of an even month, after the draw. amego: POST /json/lottery_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | Western calendar year, for example 2026. |
| period | integer | yes | Two-month period: 0 = Jan-Feb, 1 = Mar-Apr, 2 = May-Jun, 3 = Jul-Aug, 4 = Sep-Oct, 5 = Nov-Dec. |
Show the status of the invoice number ranges (字軌) that use API number assignment, for one period. Optionally one range by its API code. amego: POST /json/track_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | Western calendar year, for example 2026. |
| period | integer | yes | Two-month period: 0 = Jan-Feb, 1 = Mar-Apr, 2 = May-Jun, 3 = Jul-Aug, 4 = Sep-Oct, 5 = Nov-Dec. |
| track_api_code | string | no | API code of one number range, set in the amego back office. Omit for all ranges. |
List every invoice number range (字軌) the company holds at amego for one period: the layer, the category, the start and end numbers, and how many remain. amego: POST /json/track_all.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | integer | yes | Western calendar year, for example 2026. |
| period | integer | yes | Two-month period: 0 = Jan-Feb, 1 = Mar-Apr, 2 = May-Jun, 3 = Jul-Aug, 4 = Sep-Oct, 5 = Nov-Dec. |
Look up one allowance (折讓單) by its allowance number. amego: POST /json/allowance_query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| allowance_number | string | yes | Allowance number (折讓單編號), at most 16 characters. |
List the allowances (折讓單) of the company in a date range, one page at a time. amego: POST /json/allowance_list.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_select | yes | Which date to filter on: 1 = allowance date, 2 = creation date. | |
| date_start | string | yes | Date as YYYYMMDD, for example 20241031. |
| date_end | string | yes | Date as YYYYMMDD, for example 20241031. |
| limit | integer | no | Rows per page, 20 to 500 (default 20). |
| page | integer | no | Page number (default 1). |
Check whether the government has accepted each allowance number: the upload status and the total amount. Up to 50 numbers per call. amego: POST /json/allowance_status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| allowance_numbers | array | yes | Allowance numbers to check, up to 50. |
Get a link to the PDF of one allowance (折讓單). amego: POST /json/allowance_file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| allowance_number | string | yes | Allowance number (折讓單編號), at most 16 characters. |
Look up the registered company name for up to 20 tax IDs (統一編號), from the Ministry of Finance data. amego: POST /json/ban_query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tax_ids | array | yes | 8-digit tax IDs to look up, up to 20. |
Check whether a mobile carrier barcode (手機條碼) is valid. amego: POST /json/barcode.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| barcode | string | yes | The mobile barcode, 8 characters starting with /, for example /ABC+1+2. |
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 amego MCP by usefulapi 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 96 / 100
Release 1.0.1 · scanned 8 Nov 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 score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest26aa75baeca78c554c65e9d5c9bb9d79f8532226e21f7a19c5b01d4a129fbff2
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| 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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| amego_query_invoice | no tags | |
| amego_list_invoices | no tags | |
| amego_get_invoice_upload_status | no tags | |
| amego_get_invoice_file | no tags | |
| amego_check_lottery_invoices | no tags | |
| amego_get_track_status | no tags | |
| amego_list_track_ranges | no tags | |
| amego_query_allowance | no tags | |
| amego_list_allowances | no tags | |
| amego_get_allowance_upload_status | no tags | |
| amego_get_allowance_file | no tags | |
| amego_lookup_company_name | no tags | |
| amego_check_mobile_barcode | no tags |
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 digest26aa75baeca78c55
Scanned2026-11-08
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.0.1.
1.0.1
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 amego MCP by usefulapi 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.