ServiceNow Dev MCP (pinnintisagarSB/ServiceNow-Dev-MCP) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Emerging
74/100
2 months ago

ServiceNow Dev MCP

AI-powered ServiceNow developer toolkit for Claude Code with 116 tools covering script generation, code review, portal and catalog development, notifications, user and group management, CRUD operations, dictionary overrides, data migration, bidirectional integrations, ATF testing, performance analysis, technical documentation, and issue diagnosis.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

pinnintisagarSB

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 10 credentials: ADMIN_KEY, CREDENTIAL_ENCRYPTION_KEY, JIRA_API_TOKEN, MCP_API_KEY, SF_CLIENT_SECRET, SF_JWT_PRIVATE_KEY, SF_PASSWORD, SF_SECURITY_TOKEN, SN_OAUTH_CLIENT_SECRET, SN_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretADMIN_KEY
configALLOWED_KEYS
🔐 secretCREDENTIAL_ENCRYPTION_KEY
🔐 secretJIRA_API_TOKENyour_api_token
configJIRA_BASE_URL
configJIRA_EMAILyour_email@example.com
configJIRA_PAGE_SIZE
configLOG_LEVEL
🔐 secretMCP_API_KEY
configMCP_MODEhttp MCP_PORT=3000 node src/mcp-server.js
configMCP_PORTMCP_MODE=http =3000 node src/mcp-server.js
configMIGRATION_ENFORCE_MANDATORY
configMIGRATION_PAGE_SIZE
configMIGRATION_RUN_BUSINESS_RULES
configMIGRATION_STOP_ON_ERROR
configMIGRATION_TEST_LIMIT
configSF_API_VERSION
configSF_BULK_THRESHOLD
configSF_CLIENT_IDyour_consumer_key
🔐 secretSF_CLIENT_SECRETyour_consumer_secret
🔐 secretSF_JWT_PRIVATE_KEY
configSF_JWT_SUBJECT
configSF_LOGIN_URL
🔐 secretSF_PASSWORDyour_sf_password
🔐 secretSF_SECURITY_TOKENyour_security_token
configSF_USERNAMEyour_sf_username@example.com
configSN_INSTANCE_URL
configSN_MAX_PARALLEL_IMPORT_SETS
configSN_OAUTH_CLIENT_ID
🔐 secretSN_OAUTH_CLIENT_SECRET
🔐 secretSN_PASSWORDyourpassword
configSN_SCOPE_APP_NAME
configSN_SCOPE_PREFIX
configSN_SCOPE_TYPE
configSN_USERNAME
configSN_USE_SDK_AUTH
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deploySUPABASE_SERVICE_ROLE_KEY
deploySUPABASE_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

135/135 tools missing one or more hints — get_config (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_credential_setup_url (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); create_update_set (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +132 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

128/135 tool handlers declare input schemas (95%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

132/135 tool handlers wrap calls in try/catch (98%)

Wrap each tool handler body in try/catch and return a structured error response.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Shell command execution

6 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 8 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/pinnintisagarsb-servicenow-dev-mcp-nf1871)](https://m8ven.ai/mcp/pinnintisagarsb-servicenow-dev-mcp-nf1871)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e4b74bbba30665bd6baf3d2001a1f2ec2255b5b0
code hash: 3dad87cbf60295d93237ec053699593d6537c936febff335ffa53a3f1fa5ec25
verified: 6/19/2026, 10:52:34 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client