Skip to content

MCP servers › dev.simkit › simkit

MCP server · registry snapshot 2026-11-17 · last checked 2026-11-17

simkit MCP server

Registry name dev.simkit/simkit

by simkit.dev · domain (the registry's namespace rule)repository owner on GitHub: ealtaca (personal account)Source ↗npm ↗Website ↗

See an iOS app's network traffic, mock responses and drive the simulator through SimKit for Mac. — the publisher's description

5 of 7 record checks metversion 0.1.0-beta.1JavaScriptMITstandard input/output

Summary

dev.simkit/simkit is a local MCP server listed in the official MCP registry at version 0.1.0-beta.1, under the namespace of the domain simkit.dev. Its linked repository is github.com/ealtaca/simkit-mcp; GitHub reports its owner as ealtaca, a personal account.

Record checks

5 of 7 record checks met · 2 not checked

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • not checked: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • not checked: No known critical or high advisory in the package or its dependencies
  • #11,471 of 20,610 packages by monthly downloads, tied with 16 others
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
npm
License
MIT
Repository
public
Last tested
not tested

Tool list

Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.1.0-beta.1, published 2026-11-16 (registry, as of the 2026-11-17 snapshot)
First listed version
2026-11-16 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-17
Package and repository
checked 2026-11-17

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Not checked: listed version cannot be installed or is withdrawn (no stable release to compare the listed version against). Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-16, listed on 2026-11-17 with version 0.1.0-beta.1 (published 2026-11-16).

Source: the official MCP Registry list on 2026-11-16 and on 2026-11-17.

What it is

How do I add it to my client?

Config from the registry entry

From the npm package simkit-mcp

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "simkit": {
      "command": "npx",
      "args": [
        "-y",
        "simkit-mcp@0.1.0-beta.1"
      ]
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "simkit": {
      "command": "npx",
      "args": [
        "-y",
        "simkit-mcp@0.1.0-beta.1"
      ]
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "simkit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "simkit-mcp@0.1.0-beta.1"
      ]
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"simkit","type":"stdio","command":"npx","args":["-y","simkit-mcp@0.1.0-beta.1"]}'
Claude Code
claude mcp add --transport stdio simkit -- npx -y simkit-mcp@0.1.0-beta.1
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "simkit": {
      "command": "npx",
      "args": [
        "-y",
        "simkit-mcp@0.1.0-beta.1"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "simkit": {
      "command": "npx",
      "args": [
        "-y",
        "simkit-mcp@0.1.0-beta.1"
      ]
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.simkit]
command = "npx"
args = ["-y", "simkit-mcp@0.1.0-beta.1"]
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "simkit": {
      "command": "npx",
      "args": [
        "-y",
        "simkit-mcp@0.1.0-beta.1"
      ]
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y simkit-mcp@0.1.0-beta.1
  • Optional settings the entry also lists (left out above): SIMKIT_MCP_TOKEN.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.1.0-beta.1
Withdrawn
no

Source: registry.npmjs.org · 2026-11-17. About the version the registry lists; a manual install may resolve to a different one.

Integrity, provenance, license

Integrity
sha512-XRhWMSlaKpaj76lBb…
Signature
signed
License
MIT

Source: the package registry · 2026-11-17.

Usage

Downloads
318 in the last month

Source: api.npmjs.org · 2026-11-17.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-17.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-17. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-17. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-17. Source: read 2026-11-17.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-17. Source: read 2026-11-17.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/ealtaca/simkit-mcpOpens publiclymatchesapi.github.com · 2026-11-17

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
dev.simkit
GitHub owner
a personal account (ealtaca)
Build record
signed
Repository
github.com/ealtaca/simkit-mcp
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-17; security policy read from GitHub · 2026-11-17.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 7 record checks met · 2 not checked

  • #11,471 of 20,610 packages by monthly downloads, tied with 16 others
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • Not checkedThe version the registry lists can be installed and is not withdrawnNo stable release to compare against.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
  • Not checkedNo known critical or high advisory in the package or its dependenciesWe could not resolve its dependencies.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-17 (security policy 2026-11-17). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about dev.simkit/simkit

Answered from the data above

Who publishes dev.simkit/simkit?

The registry ties the namespace dev.simkit to the domain simkit.dev; only its owner can publish under it. Its linked repository is github.com/ealtaca/simkit-mcp; GitHub reports its owner as ealtaca, a personal account. These are facts from the registry and GitHub, not a rating.

Is dev.simkit/simkit safe to install?

We do not rate servers as safe or unsafe. 5 of its 7 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The package itself has no known vulnerability (OSV.dev). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has dev.simkit/simkit been security tested?

No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.

Does dev.simkit/simkit publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of dev.simkit/simkit?

In github.com/ealtaca/simkit-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-17; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-17
Hosting type
registry · 2026-11-17
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-17
Required credentials
none declared
registry · 2026-11-17 · no declaration is not a guarantee
Package registry
registry · 2026-11-17
Freshness
0–30 days
registry updatedAt · 2026-11-17
Lifecycle status
registry · 2026-11-17
License class
package registry · 2026-11-17
Integrity hash
declared (sri)
package registry · 2026-11-17
Signature / provenance
signed
package registry · 2026-11-17
Dependency advisories
not known (our limit)
could not resolve the dependency tree (npm install failed) - our limitation
Popularity
318 downloads a month
package registry · 2026-11-17
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9 · build record: signed
api.github.com · 2026-11-17
Maintenance
api.github.com · 2026-11-17
Environment
your machine
where it runs, from the hosting type · 2026-11-17

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “dev.simkit/simkit: MCP server record.” Data checked 2026-11-17. https://protocolprobe.com/mcp/servers/dev.simkit/simkit

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 7 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/dev.simkit/simkit)](https://protocolprobe.com/mcp/servers/dev.simkit/simkit)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology