servicenow-mcp-agent@0.5.0
VERIFIED· not startedPublisher claims: "Claude-powered agent that manages ServiceNow incidents using MCP and AWS Bedrock" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MCP_API_KEYSERVICENOW_API_KEYSERVICENOW_AUTH_METHODSERVICENOW_OAUTH_TOKENSERVICENOW_PASSWORDConfiguration, not credentials: AWS_PROFILE, AWS_REGION, DOTENV_PATH, MCP_SERVER_URL, SERVICENOW_INSTANCE_URL, SERVICENOW_USERNAME- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for MCP_API_KEY, SERVICENOW_API_KEY, SERVICENOW_AUTH_METHOD, SERVICENOW_OAUTH_TOKEN, SERVICENOW_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-18 and scored it 81/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
Requires .env to be configured with ServiceNow credentials.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."SERVICENOW_PASSWORD in your .env file.")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"(.env path: {_dotenv_path})"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.srv = _reload_server(DOTENV_PATH="/custom/path/.env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f".env file (looked in: {_dotenv_path})."Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.CMD ["servicenow-mcp-server-http", "--host", "0.0.0.0", "--port", "8000"]Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.load_dotenv(os.getenv("DOTENV_PATH", ".env"))Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.sse_url = f"{MCP_SERVER_URL.rstrip('/')}/sse"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.assert srv._dotenv_path.endswith(".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.env["DOTENV_PATH"] = str(Path(__file__).resolve().parent.parent.parent / ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."DOTENV_PATH": "", # prevent loading any .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.servicenow-mcp-server-http --host 127.0.0.1 --port 9000Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.# The .env path should be under project rootFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# chmod +x deploy.shFix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.command: servicenow-mcp-server-http --host 0.0.0.0 --port 8000Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.servicenow-mcp-server-http # defaults to 0.0.0.0:8000Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.assert srv._dotenv_path == "/custom/path/.env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.servicenow-mcp-server-http = "servicenow_mcp_agent.server_http:main_cli"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them._dotenv_path = os.getenv("DOTENV_PATH") or os.path.join(_project_root, ".env")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for servicenow-mcp-agent@0.5.0 as of 1 h ago. This is the package itself, not its dependencies.