Verlauf von vk im Namensraum io.github
io.github.bulatko/vk · Registerstatus: aktiv
Die Quelle liefert zu diesem Eintrag keinen eigenen Namen. In der Überschrift steht deshalb der hintere Teil des Bezeichners; vollständig steht er als Koordinate darunter.
Angaben zu diesem Eintrag melden
Jede veröffentlichte Änderung an diesem Eintrag, die jüngste zuerst.
| 2026-10-11 | Deklarierte Version: 0.8.2 → 0.9.0 |
|---|---|
| 2026-10-11 | Im Register geändert am (Rohangabe): 2026-10-01 → 2026-10-10 |
| 2026-10-11 | Im Register eingetragen am (Rohangabe): 2026-10-01 → 2026-10-10 |
| 2026-10-11 | Verbindungswege (Quellstruktur): {"packages":[{"registryType":"npm","identifier":"vk-mcp-server","version":"0.8.2","runtimeHint":"npx","transport":"stdio","environment":[{"name":"VK_ACCESS_TOKEN","description":"The token tools act with. To post, use a community token: Manage -> API usage -> Access tokens -> Create token (wall, photos, stories, messages, manage) — no app needed, tied to neither a browser nor an IP. It posts, comments and publishes stories, but VK refuses it wall reads; set VK_SERVICE_KEY for those. Guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md","required":false,"secret":true},{"name":"VK_SERVICE_KEY","description":"Optional service key from your VK app's settings page. Reads public profiles and walls; reads the access token is refused are made with it. Never used for writes.","required":false,"secret":true}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"npm","identifier":"vk-mcp-server","version":"0.9.0","runtimeHint":"npx","transport":"stdio","environment":[{"name":"VK_ACCESS_TOKEN","description":"The token tools act with. To post, use a community token: Manage -> API usage -> Access tokens -> Create token (wall, photos, stories, messages, manage) — no app needed, tied to neither a browser nor an IP. It posts, comments and publishes stories, but VK refuses it wall reads; set VK_SERVICE_KEY for those. Guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md","required":false,"secret":true},{"name":"VK_SERVICE_KEY","description":"Optional service key from your VK app's settings page. Reads public profiles and walls; reads the access token is refused are made with it. Never used for writes.","required":false,"secret":true}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-10-11 | Paketversionen (Rohangabe): 0.8.2 → 0.9.0 |
| 2026-10-02 | Deklarierte Version: 0.6.1 → 0.8.2 |
| 2026-10-02 | Pflicht-Geheimnisse deklariert: ja → nein |
| 2026-10-02 | Im Register geändert am (Rohangabe): 2026-07-26 → 2026-10-01 |
| 2026-10-02 | Im Register eingetragen am (Rohangabe): 2026-07-26 → 2026-10-01 |
| 2026-10-02 | Beschreibungen der Umgebungsvariablen (Rohangabe): VK_ACCESS_TOKEN=VK API access token. Quickest route if you manage a community: Manage -> API usage -> Access tokens -> Create token, ticking wall and photos — no app needed, and it is tied to neither a browser nor an IP. To act as yourself, create your own Standalone app at https://vk.com/editapp?act=create and run `npx vk-mcp-server --login <APP_ID>`. Use your own app rather than a shared ID: a token dies with the app that issued it. Full guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md → VK_ACCESS_TOKEN=The token tools act with. To post, use a community token: Manage -> API usage -> Access tokens -> Create token (wall, photos, stories, messages, manage) — no app needed, tied to neither a browser nor an IP. It posts, comments and publishes stories, but VK refuses it wall reads; set VK_SERVICE_KEY for those. Guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md · VK_SERVICE_KEY=Optional service key from your VK app's settings page. Reads public profiles and walls; reads the access token is refused are made with it. Never used for writes. |
| 2026-10-02 | Verbindungswege (Quellstruktur): {"packages":[{"registryType":"npm","identifier":"vk-mcp-server","version":"0.6.1","runtimeHint":"npx","transport":"stdio","environment":[{"name":"VK_ACCESS_TOKEN","description":"VK API access token. Quickest route if you manage a community: Manage -> API usage -> Access tokens -> Create token, ticking wall and photos — no app needed, and it is tied to neither a browser nor an IP. To act as yourself, create your own Standalone app at https://vk.com/editapp?act=create and run `npx vk-mcp-server --login <APP_ID>`. Use your own app rather than a shared ID: a token dies with the app that issued it. Full guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md","required":true,"secret":true}],"additional_arguments_declared":false}],"remotes":[]} → {"packages":[{"registryType":"npm","identifier":"vk-mcp-server","version":"0.8.2","runtimeHint":"npx","transport":"stdio","environment":[{"name":"VK_ACCESS_TOKEN","description":"The token tools act with. To post, use a community token: Manage -> API usage -> Access tokens -> Create token (wall, photos, stories, messages, manage) — no app needed, tied to neither a browser nor an IP. It posts, comments and publishes stories, but VK refuses it wall reads; set VK_SERVICE_KEY for those. Guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md","required":false,"secret":true},{"name":"VK_SERVICE_KEY","description":"Optional service key from your VK app's settings page. Reads public profiles and walls; reads the access token is refused are made with it. Never used for writes.","required":false,"secret":true}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-10-02 | Paketversionen (Rohangabe): 0.6.1 → 0.8.2 |
| 2026-10-02 | Geheime Pflichtvariablen (Rohangabe): VK_ACCESS_TOKEN → – |
| 2026-10-02 | Umgebungsvariablen (Rohangabe): VK_ACCESS_TOKEN → VK_ACCESS_TOKEN, VK_SERVICE_KEY |
| 2026-09-08 | Verbindungswege (Quellstruktur): – → {"packages":[{"registryType":"npm","identifier":"vk-mcp-server","version":"0.6.1","runtimeHint":"npx","transport":"stdio","environment":[{"name":"VK_ACCESS_TOKEN","description":"VK API access token. Quickest route if you manage a community: Manage -> API usage -> Access tokens -> Create token, ticking wall and photos — no app needed, and it is tied to neither a browser nor an IP. To act as yourself, create your own Standalone app at https://vk.com/editapp?act=create and run `npx vk-mcp-server --login <APP_ID>`. Use your own app rather than a shared ID: a token dies with the app that issued it. Full guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md","required":true,"secret":true}],"additional_arguments_declared":false}],"remotes":[]} |
| 2026-08-26 | Beschreibung (Rohangabe): – → VK (VKontakte): read walls, users, communities and stats; publish, edit and comment on posts. |
| 2026-08-16 | Im Register geändert am (Rohangabe): – → 2026-07-26 |
| 2026-08-16 | Im Register eingetragen am (Rohangabe): – → 2026-07-26 |
| 2026-08-16 | Statusmeldung des Registers (Rohangabe): – → – |
| 2026-08-16 | Schemafassung des Rohsatzes (Rohangabe): – → https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json |
| 2026-08-16 | Symbolformate (Rohangabe): – → – |
| 2026-08-16 | Beschreibungen der Umgebungsvariablen (Rohangabe): – → VK_ACCESS_TOKEN=VK API access token. Quickest route if you manage a community: Manage -> API usage -> Access tokens -> Create token, ticking wall and photos — no app needed, and it is tied to neither a browser nor an IP. To act as yourself, create your own Standalone app at https://vk.com/editapp?act=create and run `npx vk-mcp-server --login <APP_ID>`. Use your own app rather than a shared ID: a token dies with the app that issued it. Full guide: https://github.com/bulatko/vk-mcp-server/blob/master/docs/SETUP.md |
| 2026-08-16 | Formate der Umgebungsvariablen (Rohangabe): – → – |
| 2026-08-16 | Bereitstellungsform (Rohangabe): – → paket |
| 2026-08-16 | Remote-Hosts (Rohangabe): – → – |
| 2026-08-16 | Remote-Adressen (Rohangabe): – → – |
| 2026-08-16 | Laufzeithinweise (Rohangabe): – → npx |
| 2026-08-16 | Paketversionen (Rohangabe): – → 0.6.1 |
| 2026-08-16 | Paketbezeichner (Rohangabe): – → vk-mcp-server |
| 2026-08-16 | Repository-Unterordner (Rohangabe): – → – |
| 2026-08-16 | Repository-Plattform (Rohangabe): – → github |
| 2026-08-16 | Pfad-Umgebungsvariablen (Rohangabe): – → – |
| 2026-08-16 | Geheime Pflichtkopfzeilen (Rohangabe): – → – |
| 2026-08-06 | Deklarierte Version: – → 0.6.1 |
| 2026-08-06 | Repository-Adresse geführt: – → ja |
| 2026-08-06 | Pfadargument vorhanden: – → nein |
| 2026-08-06 | Ausführungsort: – → lokal |
| 2026-08-06 | Pflicht-Geheimnisse deklariert: – → ja |
| 2026-08-06 | Paketquellen (Rohangabe): – → npm |
| 2026-08-06 | Repository (Rohangabe): – → https://github.com/bulatko/vk-mcp-server.git |
| 2026-08-06 | Pfadargumente (Rohangabe): – → – |
| 2026-08-06 | Transportarten (Rohangabe): – → stdio |
| 2026-08-06 | Geheime Pflichtvariablen (Rohangabe): – → VK_ACCESS_TOKEN |
| 2026-08-06 | Umgebungsvariablen (Rohangabe): – → VK_ACCESS_TOKEN |
tracevero · https://tracevero.de/mcp/io-github-bulatko-vk/aenderungen