github.com/airtasker/airtasker-mcp-server · main · scanned 2 h ago · 1 config file

1 agent component (1 MCP server) in airtasker/airtasker-mcp-server, nothing alarming.

Components11 MCP server
High blast radius0credentials, shell or unvetted code
Credentials handed to agents0none seen
Not vetted0of 0 local servers, skills and plugins · 1 hosted
ComponentWhereVerdictBlast radius
airtaskerMCP server · Claude Code · httpmcp.airtasker.com
.mcp.jsonhosted · no package
low
  • sends the agent's tool calls and their data to mcp.airtasker.com
  • is not a registry package, so there is no verdict to check
What to do about it
  • Hosted servers have no package to run in the sandbox. Everything the agent sends them goes to that host, so treat the credential as the trust decision. Teams can watch a hosted server's tool list for changes.
  • For a whole organization (every repo and laptop, rescanned daily, with removal across machines), see Discovery for teams.
Share: https://killerskills.ai/scan/github/airtasker/airtasker-mcp-serverRescan nowScan another