assess-crew-risk
Assesses a URL under a web-crawling compliance risk framework.
LABSCO SUMMARY
The date tool is here because relative dates are the quiet failure in an agent chain, and it pins a timezone rather than trusting one.
get-current-date is fixed to Asia/Shanghai at UTC+8 and returns yyyy-MM-dd, which makes "tomorrow" resolvable to a value a downstream tool will take rather than to whatever the model assumed. assess-crew-risk is why the server exists: it takes a URL and returns an assessment under a crawling-compliance framework, which is a thing worth running before a scrape rather than after a complaint.
What it is
A two-tool compliance helper: one assesses a URL under a web-crawling compliance risk framework, and one returns the current date in the Asia/Shanghai timezone so relative dates in a request resolve to something real.
What you get
- assess-crew-risk evaluates a URL under a web-crawling compliance risk framework.
- get-current-date returns the current date as yyyy-MM-dd in the Asia/Shanghai timezone at UTC+8, so phrases such as tomorrow or next Wednesday can be turned into a date another tool will accept.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y mcp-crew-risk
USE CASES
01
Checking whether scraping a site is likely to be a compliance problem
The assessment takes the URL itself, so the question is answered before a crawler is pointed at it.
02
Resolving a relative date before handing it to another tool
A fixed timezone and a fixed format mean "next Wednesday" becomes a date the next call will accept, rather than one the model guessed.
2 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get-current-date
Returns the current date as yyyy-MM-dd in the Asia/Shanghai timezone at UTC+8, so relative dates such as tomorrow or next Wednesday can be resolved before another tool is called.
BEFORE YOU INSTALL
What to know first
Tools you get
2 tools when we connected. The Features headings describe facets of the single assess-crew-risk check, not separate tools; get-current-date is undocumented.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 2 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-crew-risk": {
"command": "npx",
"args": [
"-y",
"mcp-crew-risk"
]
}
}
}npx
TERMINAL
npx -y mcp-crew-risk
