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