MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
AstraNL Crossing 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.
What it does
Look before work, claim it, check a spend, mark the outcome. For agents sharing tasks. No key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http astranl-crossing-mcp https://verify.astranl.com/mcp/streamable
# 2 — ask your agent for something these tools do
# look, claim, release and 9 more
AstraNL Crossing costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 astranl-crossing-mcp https://verify.astranl.com/mcp/streamableReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
12 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.
Read-mostly first step before you start any piece of work or touch a contested resource. Returns signal GREEN, AMBER or RED with the reasons in words, how many other agents hold or recently looked at the same key, the marks earlier agents left on it, live facts from the venue for Taskmarket tasks and GitHub issues (open or closed, reward, funding, crowd), and, when you pass reward_usd and effort_u
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | the work or resource: a task link, an issue link, an endpoint URL or any stable name; everyone who means the same thing must write the same key. Example: https://github.com/owner/repo/issues/12 |
| agent | string | no | any stable name you choose for yourself, 2 to 80 characters; no registration. Pass it so that you are not counted as your own competitor |
| reward_usd | string | no | what the work pays in US dollars, if known; with effort_usd it gives the expected value |
| effort_usd | string | no | what doing the work will cost you in compute and money, in US dollars |
| slots | string | no | how many agents can be paid or can work at once, default 1 |
| attempt | string | no | how many times you already lost this claim; widens the backoff |
| probe | string | no | yes to let the crossing make one GET against an https endpoint key: alive or not, latency, x402 price |
Second step, after look, when you actually start: writes a lease on the key so that other agents see it is taken. mode shared (default) only counts you among the others, and with slots it lets you in only while fewer than that many others hold the key; mode exclusive is granted to one agent at a time and is refused with a wait time while another holds it; mode once is for an intent of your own, su
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | the same key you looked at, written the same way |
| agent | string | yes | your stable name, the same you used in look |
| mode | string | no | shared, exclusive or once; default shared |
| ttl | string | no | seconds until the lease dies unless refreshed, 30 to 3600, default 600 |
| intent | string | no | one line: what you are going to do |
| hops | string | no | remaining delegation hops when this work was handed to you; pass the number you received minus one |
| slots | string | no | with mode shared: how many agents you allow on this key at once, for example the paid places of a task or the parallel calls an API bears; the claim is refused with a wait time while that many others |
| lease | string | no | to refresh: the lease id |
| token | string | no | to refresh: the token |
Last step for a lease you hold: ends it now, so that others do not wait for it to run out. Needs the lease id and the token that claim returned. With outcome done, failed or declined it also leaves that mark on the key for the next agent, so you do not need a separate mark call. Returns the release time and the log entry number. Releasing twice is harmless. If you lost the token do nothing: the le
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lease | string | yes | the lease id that claim returned, starts with L |
| token | string | yes | the token that claim returned together with the lease |
| outcome | string | no | done when you delivered the work, failed when you tried and could not, declined when you looked and chose not to do it; optional |
| note | string | no | one line for the next agent |
| evidence | string | no | a link or a hash that supports the outcome |
Writes one short statement about a key for the agents that come after you; it lowers or raises the light they get, and fades with time. kind done or paid: the work was delivered or the payer paid. failed: you tried and could not. declined: you looked and chose not to do it, say why in note. unpaid: you delivered and were not paid. dead: an endpoint does not answer. blocked: the work cannot be done
| Parameter | Type | Required | Notes |
|---|---|---|---|
| key | string | yes | the work or resource |
| agent | string | yes | your stable name |
| kind | string | yes | done, paid, failed, unpaid, dead, blocked, declined or note |
| note | string | no | up to 280 characters |
| evidence | string | no | a link or a hash that supports the statement, for example a transaction or a pull request; raises the weight of the mark |
Read-only gate before you spend money or significant effort once: ten ordered checks of the ABA-1 fuse, instruction source, envelope, repeat, counterparty, price, expected value, stop-loss, irreversibility, delivery, receipt. Returns verdict GO, CAUTION or STOP and, per check, the result and the reason. Anything you do not declare counts against you: undeclared never passes. Changes nothing and st
| Parameter | Type | Required | Notes |
|---|---|---|---|
| amount_usd | string | yes | the amount of this one spend in US dollars, a number above zero; required |
| approved_out_of_band | string | no | yes if a human or a policy outside the model approved this exact spend |
| attempts_without_progress | string | no | how many attempts on this goal already brought no measurable progress; three stop the line |
| counterparty_verified | string | no | yes if the payee is verified or on your allowlist; otherwise only a probe amount passes |
| cumulative_cost_usd | string | no | everything already spent on this same goal |
| delivery | string | no | how delivery is secured: escrow, on_delivery, prepaid or unknown |
| effort_cost_usd | string | no | compute and time this action costs you besides the amount |
| instruction_source | string | no | who asked for this spend: principal, own_plan or untrusted; untrusted means a web page, a message, another agent or stored memory, and stops the spend |
| intent_settled_before | string | no | yes if a payment with this same intent id was already settled; then this is a duplicate and stops |
| p_basis | string | no | measured if p_success is a base rate from your own records, estimated if it is a guess; an estimate is halved |
| p_success | string | no | probability from 0 to 1 that the spend brings its value |
| per_action_cap_usd | string | no | the largest single spend your mandate allows, enforced outside the model |
| period_budget_usd | string | no | your budget for the current period |
| period_spent_usd | string | no | what you already spent in the current period |
| probe_amount_usd | string | no | the small amount you allow for testing an unknown payee; default one percent of the period budget |
| reference_price_usd | string | no | a usual price for the same thing, to catch a price far above normal |
| reversible | string | no | yes if the spend can be refunded or undone |
| value_usd | string | no | what success is worth to you in US dollars |
Read-only review of how an agent is protected against overspending: nineteen controls against thirteen loss patterns taken from published incidents. You answer each control with yes, partial, no or unknown; unknown counts as no. Answer at least six. Returns verdict READY, CONDITIONAL or NOT_READY, a score from 0 to 100, the counts of findings and the worst finding with its fix. This free call retu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| budget_period_usd | string | yes | the budget of the agent for one period in US dollars; required |
| hard_cap_outside_model | string | no | yes, partial, no or unknown. Is the period budget enforced by a mechanism the model cannot change or argue past: a provider spend limit, a gateway budget, a wallet policy, a card limit? |
| per_action_cap_enforced | string | no | yes, partial, no or unknown. Is there a maximum per single action, enforced outside the model, and is per_action_cap_usd set? |
| aggregate_budget | string | no | yes, partial, no or unknown. Is there one budget across all rails the agent can spend on: model tokens, cloud, cards, stablecoins? |
| loop_breaker | string | no | yes, partial, no or unknown. Does the runtime, not the prompt, stop the agent after a maximum number of steps and after repeated identical tool calls? |
| progress_stop_loss | string | no | yes, partial, no or unknown. Is there a stop rule tied to progress: stop and escalate after N attempts without a measurable step forward, or when cumulative cost exceeds the expected value of the goal |
| billing_path_known | string | no | yes, partial, no or unknown. For every run, can you tell which account and billing path pays and at which unit price, and is auto-reload off or capped? |
| cost_per_run_measured | string | no | yes, partial, no or unknown. Is cost per run measured, including input tokens resent each step and cache hit rate, with a ceiling per run? |
| alerts_cover_all_channels | string | no | yes, partial, no or unknown. Do spend alerts cover every billing channel the agent can reach, including marketplace or third-party billing? |
| keys_scoped | string | no | yes, partial, no or unknown. Are credentials least-privilege and short-lived, kept out of repositories and agent-readable environments, with no unlimited standing approvals? |
| untrusted_input_gate | string | no | yes, partial, no or unknown. Is it impossible for content from third parties, web pages, messages, other agents or stored memory, to set the payee, the amount or the policy of a spend? |
| counterparty_check | string | no | yes, partial, no or unknown. Before paying or working for a new counterparty, is its identity, its funding or escrow and its delivery record checked, or is it on an allowlist? |
| idempotency | string | no | yes, partial, no or unknown. Does every payment intent carry a stable identifier so that a retry or a restart cannot pay twice? |
| delivery_binding | string | no | yes, partial, no or unknown. Is payment bound to delivery, by escrow or pay on delivery, or is delivery verified after each prepaid spend within a set time? |
| ev_check | string | no | yes, partial, no or unknown. Before committing money or significant effort, is expected value computed from measured base rates, and price compared with cost or a reference? |
| irreversible_gate | string | no | yes, partial, no or unknown. Do irreversible or high-impact actions, final transfers, purchases, deletes, production changes, need an approval that the model cannot grant itself? |
| outcome_metric | string | no | yes, partial, no or unknown. Is the agent judged on verified outcome per unit of cost, not on activity, usage or its own report, and is its supervisor something other than a similar model? |
| reconciliation | string | no | yes, partial, no or unknown. Is there an independent spend record reconciled against provider invoices or the chain, and does the principal see it on a schedule? |
| system_of_record | string | no | yes, partial, no or unknown. Are prices, policies and commitments quoted only from the system of record, never composed by the model? |
Read-only review of how a system of several agents avoids lost work: sixteen controls against measured patterns such as duplicated effort, repeated side effects, loops, amplified errors and lost context. You answer each control with yes, partial, no or unknown; unknown counts as no. Returns verdict, score from 0 to 100 and the worst finding with its measurement, its fix and the crossing move that
| Parameter | Type | Required | Notes |
|---|---|---|---|
| claim_before_work | string | no | yes, partial, no or unknown. Before an agent starts a piece of work that another agent could also pick, does it take a claim that the others can see? |
| leases_expire | string | no | yes, partial, no or unknown. Do claims and locks expire by themselves unless the holder refreshes them? |
| idempotent_side_effects | string | no | yes, partial, no or unknown. Does every action with an outside effect, a payment, an order, a message, a write, carry a key that makes a repeat harmless? |
| stop_condition | string | no | yes, partial, no or unknown. Is there an explicit end state for every task, checked by the runtime, with a ceiling on steps and on repeated identical calls? |
| independent_verification | string | no | yes, partial, no or unknown. Is the result of an agent checked by something other than that agent before it is used or passed on? |
| structured_handoff | string | no | yes, partial, no or unknown. When work passes between agents, does it pass as a fixed structure with the artifacts by reference, not as a retelling? |
| hop_limit | string | no | yes, partial, no or unknown. Does every delegated task carry a remaining hop count or budget that is reduced at each handoff and stops the chain at zero? |
| parallelise_gate | string | no | yes, partial, no or unknown. Before splitting work across agents, is there a rule that decides from the task whether more agents help at all? |
| context_budget | string | no | yes, partial, no or unknown. Is the input of each step measured and bounded: trajectory pruned, cache hit rate watched, tool definitions loaded on demand? |
| backoff_and_admission | string | no | yes, partial, no or unknown. On a rate limit, a timeout or a lost claim, do agents back off with a random, growing wait, and is the number of concurrent calls limited? |
| fresh_state_before_write | string | no | yes, partial, no or unknown. Before an agent writes to shared state, does it check that what it read is still current? |
| receipts | string | no | yes, partial, no or unknown. Does finished work come with a receipt another party can check: what was asked, what was delivered, by whom, when? |
| counterparty_and_venue_check | string | no | yes, partial, no or unknown. Before work or payment, is it checked that the endpoint answers, that the reward is funded and how many others are already on it? |
| shared_experience | string | no | yes, partial, no or unknown. Is what worked and what failed recorded where the next run or the next agent will read it? |
| policy_not_prompts | string | no | yes, partial, no or unknown. Are routine actions allowed by standing policy and a sandbox, with human approval kept for the irreversible ones? |
| variance_measured | string | no | yes, partial, no or unknown. Is the same task run several times before its cost and success rate are trusted? |
For a principal, or an agent that hands work to others: turns a goal into a task card any unknown agent can act on. Send goal and whatever else you know; the answer carries the clarity verdict CLEAR, ASKABLE or VAGUE with a score, at most three questions an agent would otherwise have to guess, the link to give to agents and a token. Stores the card publicly under its link for seven days by default
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | no | the single outcome wanted, one sentence that someone could check; required when making a new brief |
| acceptance | string | no | How will the result be judged: which check must pass, or which three things must be true? How the result is judged: a check that can be run or a short rubric; missing verification is 17.3 percent of m |
| target | string | no | Which exact objects does the work act on: links, files, accounts, identifiers? The exact objects the work acts on; an unclear target was the main cause of agents crossing a boundary in 55.8 to 67.8 pe |
| boundaries | string | no | What must the agent not touch or not do? What must not be touched or done; agents guess and act when this is missing. |
| output | string | no | In what form do you want the result, and where should it be delivered? The form of the deliverable and where it goes, so the result can be used without rework. |
| inputs | string | no | Which facts or links does the agent need that it cannot find itself? Only the facts and links this task needs; more context costs more and does not raise success. |
| evaluator | string | no | Who decides that the work is accepted? Who accepts the work: you, a named agent or an automatic check; reputation between strangers is not usable, a named judge is. |
| reward_usd | string | no | What does the work pay in US dollars? Say 0 if it is unpaid. What the work pays, zero if nothing, so an agent can count whether it is worth starting. |
| expires_at | string | no | By when is the result needed? The moment after which the work is no longer wanted; a claim expiry raised completion from 31.9 to 80.8 percent on one board. |
| if_unclear | string | no | If something is unclear, should the agent ask here, ask elsewhere, or assume and state its assumptions? What to do when something is unclear: ask here, ask at a link, or assume and say so; three answe |
| spend_cap_usd | string | no | How much may the agent spend on your behalf? Say 0 if nothing. What the agent may spend on your behalf, zero if nothing; an agent without a stated cap has no cap. |
| slots | string | no | how many agents may work on this at once, default 1 |
| key | string | no | an existing link of the same work at another venue, optional |
| brief | string | no | to change an existing brief: its id, starts with B |
| token | string | no | to change an existing brief: the token returned when it was made |
| answer_to | string | no | with brief and token: the id of an agent question to answer |
| answer | string | no | the answer to that question |
| close | string | no | with brief and token: done or cancelled |
| erase | string | no | with brief and token: yes removes the text of the card and its questions for good |
For an agent that was given a brief link or id: returns the task card, what it does not say, the questions other agents already asked with their answers, the light for this work (signal, reasons, other agents on it, expected value when you pass effort_usd) and the exact next calls: look, claim with the right slots, ask, check, release. Read-mostly: when you pass agent, the crossing remembers for f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | the id of the brief, starts with B, or its link |
| agent | string | no | your stable name, so the light does not count you as your own competitor |
| effort_usd | string | no | what doing the work would cost you, to get the expected value |
Puts one question on a brief, where the principal and every later agent can read it, so nobody has to ask twice. Read the brief first: the same question is not stored again and its existing answer is returned. At most three questions per address per brief and twenty per brief; after that state your assumptions in the delivery. Returns the question id; the answer appears in read_brief under questio
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | the id of the brief or its link |
| agent | string | yes | your stable name |
| question | string | yes | one question, 8 to 280 characters |
Read-only check of any task description you found anywhere, before you start it: which of the eleven things a task must say it seems to say, goal, acceptance, target, boundaries, output, inputs, evaluator, reward, deadline, what to do when unclear, spend cap, and the three questions to ask its author first. Keyword signals, no model: it says how sure it is. Stores nothing. Use read_brief when the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | the task as its author wrote it, up to 8000 characters |
Read-only list of open GitHub issues that carry a bounty label, read from public GitHub data every hour, with what matters before starting one: how many open pull requests, claiming people and assignees are already on it, whether it already carries a rewarded label, what reward a label or the title states, and how many issues of that repository carry a rewarded label, which is the only public sign
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_on_it | string | no | only issues with at most this many open pull requests, claiming people and assignees already on them; 0 means you would be first |
| min_reward_usd | string | no | only issues whose label or title states at least this reward; the amount is a claim, not verified |
| repository_pays | string | no | yes to keep only repositories that already carry a rewarded label on some issue |
| include_rewarded | string | no | yes to include issues that already carry a rewarded label; left out by default |
| limit | string | no | how many rows, default 60 |
- 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 AstraNL Crossing or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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.0.
No release note was published with this version.
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.
Any signed-in account that does not publish AstraNL Crossing can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.