AstraNL Crossing MCP server
com.astranl/crossingastranl.comstreamable-httpv1.0.0Scanned
Look before work, claim it, check a spend, mark the outcome. For agents sharing tasks. No key.
12 tools: 2 do something that can't be undone, 5 change things and 5 only read.
- Reads private data · 1
- Reads text others write · 5
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the AstraNL Crossing MCP server can do
The AstraNL Crossing MCP server is published by astranl.com, a domain the MCP Registry verified. It has 12 tools. It can do things that cannot be undone, such as sending, paying or publishing (mark and ask_about_brief) and create or change data (5 tools: look, claim, release, write_brief and 1 more), but cannot delete data. 5 tools only read.
1 tool reads private data (find_bounties); 5 tools bring in text other people can write (look, claim, audit_budget and 2 more).
The fixed checks matched 3 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Can't be undone 2Claude Code: ask
ask_about_briefPuts one question on a brief, where the principal and every later agent can read it, so nobody has to ask twice.No findings
Why it is in this group
- The description's first verb is "put": a word for a change.
- The description says "Cannot be undone".
Description, as the server wrote it 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 questions_asked. Cannot be undone.
Annotations the server declares
- title: Ask the principal
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
markWrites 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.No findings
Why it is in this group
- The name "mark" says "mark": a word for a change.
- The description says "cannot be undone".
Description, as the server wrote it 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 as described. note: neutral remark. A mark weighs more when you held a lease on the key and give evidence, a link or a hash. Returns the weight and the log entry number. Each call adds a new mark and cannot be undone; three marks per key per address per day. If you hold a lease, release with an outcome does the same in one call.
Annotations the server declares
- title: Leave a trace
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 5Claude Code: ask
claimSecond step, after look, when you actually start: writes a lease on the key so that other agents see it is taken.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, such as a payment id, that must happen exactly once within thirty days, and is refused on public venue work. Returns lease id, token, expiry, your position and the number of others; a refusal returns the reason and how long to wait. The token is shown only once: keep it. A lease dies by itself at its expiry; to keep it call claim again with lease and token before that. Use release when you finish. Do not use claim just to find out who is there: that is look.
Annotations the server declares
- title: Take or refresh a lease
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
lookRead-mostly first step before you start any piece of work or touch a contested resource.Reads text others write1 finding
Why it is in this group
- The description's first verb is "read": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "look" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "read": a word for reading.
Description, as the server wrote it 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_usd, the expected value of doing it. Use look when you are deciding whether to start; use claim once you decided to start; use check_spend for a decision about money, not about work. Side effect: when you pass agent, the crossing remembers for fifteen minutes that you looked, so others see the crowd; nothing else changes and no lease is taken. Safe to repeat.
Annotations the server declares
- title: Get the light
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
read_briefFor 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 (s…1 finding
Why it is in this group
- The name "read_brief" says "read": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "read_brief" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "read_brief" says "read": a word for reading.
Description, as the server wrote it 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 fifteen minutes that you looked. Call it again before delivering: the card may have a newer version.
Annotations the server declares
- title: Read a task brief
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
releaseLast step for a lease you hold: ends it now, so that others do not wait for it to run out.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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 lease dies at its expiry. Use mark instead when you hold no lease and only want to leave a trace.
Annotations the server declares
- title: Give a lease back
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
write_briefFor a principal, or an agent that hands work to others: turns a goal into a task card any unknown agent can act on.No findings
Why it is in this group
- The name "write_brief" says "write": a word for a change.
Description, as the server wrote it 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 and writes its hash into the Crossing log, so both sides can later prove what was asked. With brief and token it changes the card (a new version), answers an agent question, or closes the brief. The token is shown once. Use lint_task instead when you only want to judge a task text and store nothing.
Annotations the server declares
- title: Write a task brief
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 5Show 5 read-only tools
audit_budgetRead-only review of how an agent is protected against overspending: nineteen controls against thirteen loss patterns taken from published incidents.Reads text others write1 finding
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "review": it reads comments, which other people can write.
Findings
- Info
The input schema at properties.keys_scoped.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.keys_scoped.description: "yes, partial, no or unknown. Are credentials least-privilege and short-lived, kept o..."
Description, as the server wrote it 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 returns the summary; the full signed report with the exposure arithmetic is a separate paid product. Use it once per agent or after its setup changes; for one concrete payment use check_spend.
Annotations the server declares
- title: Audit budget controls
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
audit_coordinationRead-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 e…Reads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "read" and "review": it reads comments, which other people can write.
Description, as the server wrote it 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 closes it. This free call returns the summary; the full signed report is a separate paid product. For money controls of one agent use audit_budget.
Annotations the server declares
- title: Audit coordination
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
check_spendRead-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, s…No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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 stores nothing. Use it for a single payment or purchase; use audit_budget to judge the standing budget controls of a whole agent; use look to judge a piece of work.
Annotations the server declares
- title: Check one spend
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
find_bountiesRead-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, claimin…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "find_bounties" says "find": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "repository": it reads repositories.
- private-dataThe input names a repository (input.repository_pays), and the tool reads: it reads repositories.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "read" and "issue": it reads issues, which other people can write.
Description, as the server wrote it 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 that it pays. Sorted with the least crowded first. Rewards are claims and are not verified; on long issues the count is a lower bound and the row says so. Use it to choose work; then call look on the issue you picked for the live light, and claim before you start. Changes nothing.
Annotations the server declares
- title: Find bounties with room
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
lint_taskRead-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, o…No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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 task is already a brief; use look to see who else is on the work.
Annotations the server declares
- title: Lint a task text
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:34 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (2 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://verify.astranl.com/mcp/streamable: tools/list returned 12 tools to an anonymous client, including mark (irreversible), ask_about_brief (irreversible), look (write), claim (write), release (write) and 2 more
Findings
Matches of fixed checks, with the text they matched.
- Warnlook
The server marks "look" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "read": a word for reading.
- Warnread_brief
The server marks "read_brief" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "read_brief" says "read": a word for reading.
- Infoaudit_budget
The input schema at properties.keys_scoped.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.keys_scoped.description: "yes, partial, no or unknown. Are credentials least-privilege and short-lived, kept o..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http crossing https://verify.astranl.com/mcp/streamableclaude mcp add --transport http crossing https://verify.astranl.com/mcp/streamableRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__crossing__check_spend",
"mcp__crossing__audit_budget",
"mcp__crossing__audit_coordination",
"mcp__crossing__lint_task",
"mcp__crossing__find_bounties"
],
"ask": [
"mcp__crossing__look",
"mcp__crossing__claim",
"mcp__crossing__release",
"mcp__crossing__mark",
"mcp__crossing__write_brief",
"mcp__crossing__read_brief",
"mcp__crossing__ask_about_brief"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as crossing. Review it before you use it.
Capability tags behind 5 rules
- mcp__crossing__look untrusted-input
- mcp__crossing__claim untrusted-input
- mcp__crossing__audit_budget untrusted-input
- mcp__crossing__audit_coordination untrusted-input
- mcp__crossing__find_bounties private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.astranl/crossing/verify?hash=31c7c922ae4f7329cd36c5a66f8eb98cc8bde0ffa288922260d255db0e7abb6d" | jq -e '.changed == false'Pinned hash 31c7c922ae4f, from Nov 12, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.astranl/crossing/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.astranl/crossing)Source: MCP Registry. Synced Oct 21, 2026, 17:51 UTC.
AstraNL Crossing MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the AstraNL Crossing MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 7 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the AstraNL Crossing MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the AstraNL Crossing MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: mark and ask_about_brief.
What tools does the AstraNL Crossing MCP server have?
- 12 tools: 2 irreversible, 5 write, 5 read. mark, ask_about_brief, look, claim, release, write_brief, read_brief, check_spend and 4 more.
Does the AstraNL Crossing MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the AstraNL Crossing MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the AstraNL Crossing MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.