MCP servers › io.github.hpdkhoa › poselab-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.hpdkhoa/poselab-mcp

Measured spatial answers for posing first-person arms and a rifle in Blender — the publisher's description

7 of 8 record checks metRead-only · tools listed 2026-10-23Topic: media-and-design · AI-classifiedversion 0.7.0PythonMITstandard input/output31 tools

Summary

io.github.hpdkhoa/poselab-mcp is a local MCP server listed in the official MCP registry at version 0.7.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 31 tools, 0 resources and 0 prompts.

Record checks

7 of 8 record checks met · 1 does not apply

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
met: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 1 star (ranked from 10)

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

Key facts

Runs: local package
Transport: standard input/output
Package: PyPI · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 31
Described as changing data: 16 of 31 toolsAI-classified
Topic: media-and-designAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

16 tools are described as changing something (pose_idle, pose_clip, move_part, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.7.0, published 2026-10-14 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-08 (earliest version still in the registry; older removed versions would be earlier)

Version history

9 versions listed, 2026-10-08 to 2026-10-14; 9 in the 90 days before the 2026-10-23 snapshot.

Most recent 9 versions

0.7.0 · 2026-10-14
0.6.0 · 2026-10-14
0.5.0 · 2026-10-13
0.4.0 · 2026-10-10
0.3.1 · 2026-10-09
0.3.0 · 2026-10-08
0.2.2 · 2026-10-08
0.2.1 · 2026-10-08
0.2.0 · 2026-10-08

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.7.0 (published 2026-10-14).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

31tools

0resources

0prompts

16 of 31 tools are described as changing something (creating, editing, deleting, sending or running).

list_rigsreads or searches
“The rigs to load: the built-in sample and those in the rigs file (POSELAB_RIGS).”
Takes no inputs.
load_rigreads or searches
“Loads a rig: the arms on their idle pose, the rifle on the gun bone, its clips.”
1 input, 1 required
- rigstringrequired
describeon 23 other serversreads or searches
“What is loaded and the conventions every tool uses.”
Takes no inputs.
pose_idledescribed as changing data
“The arms back on the idle pose, every rifle part home.”
Takes no inputs.
pose_clipdescribed as changing data
“The arms as a clip has them at a time in seconds.”
2 inputs, 2 required
- clipstringrequired
- secondsnumberrequired
move_partdescribed as changing data
“Draws a moving part of the rifle (such as carrier) back along the barrel, cm from home.”
2 inputs, 2 required
- partstringrequired
- cmnumberrequired
move_gundescribed as changing data
“Moves the rifle from where it stands: roll + turns its right side up (about the bore); swing + takes the muzzle left, pitch + the muzzle up (about the pivot); right, forward, up move it in the view, …”
8 inputs
- rollnumber
- swingnumber
- pitchnumber
- rightnumber
- forwardnumber
- upnumber
- pivotstring or array“a rig point (stock, bore) or [x, y, z] in the gun frame”
- keep_handsarray“hands that keep their hold on the rifle as it moves (arm IK)”
reachon 2 other serversdescribed as changing data
“Puts a wrist on a point by arm IK; the hand keeps its turn.”
4 inputs, 2 required
- sidestringrequired
- targetstring or arrayrequired“a name (a bone such as hand_l, a fingertip such as index_tip_l, a rig point such as port) or [x, y, z] in the frame”
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”
- polearray or null“where the elbow points, arms frame cm”
turn_bonedescribed as changing data
“Turns one bone by degrees about an axis through its head; the bones below it follow and nothing else moves.”
4 inputs, 3 required
- bonestringrequired
- axisarrayrequired“[x, y, z]: the axis's direction in the frame”
- degreesnumberrequired
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”
snapshoton 24 other serverscreates or changes datadescribed as changing data
“Saves or loads a named pose (the arms and the rifle's parts).”
2 inputs, 2 required
- actionstringrequired
- namestringrequired
wherereads or searches
“Where bones, fingertips (<finger>_tip_<l|r>) and rig points are, in a frame.”
2 inputs, 1 required
- namesarrayrequired
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”
distanceon 3 other serversreads or searches
“The distance between two points, cm, and b minus a in the frame.”
3 inputs, 2 required
- astring or arrayrequired“a name (a bone such as hand_l, a fingertip such as index_tip_l, a rig point such as port) or [x, y, z] in the frame”
- bstring or arrayrequired“a name (a bone such as hand_l, a fingertip such as index_tip_l, a rig point such as port) or [x, y, z] in the frame”
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”

Show 19 more tools

clearancereads or searches
“How deep the rifle sits inside the arms (capsules: forearm 3 cm, palm 1.8 cm, finger segments 0.75 cm).”
4 inputs
- partsstring
- ignorearray“segment names, prefixes or wildcards to leave out (thumb, index3_r, *_l)”
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”
- topinteger
anatomyreads or searches
“Each arm against the human arm's limits.”
2 inputs
- sidestring
- fingersboolean
gripreads or searches
“How each hand touches the rifle: with the palm or with the back.”
10 inputs
- sidestring
- back_max_cmnumber
- palm_max_cmnumber
- hold_within_cmnumber
- palm_within_cmnumber
- holdboolean
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”
- graspboolean
- contact_cmnumber
- frictionnumber
arm_rangesreads or searches
“The research behind anatomy's limits: for each joint of the arm (shoulder, elbow, forearm, wrist, finger knuckle, middle and end joints, thumb), the AAOS normal range (the 1965 table; tables_differ s…”
Takes no inputs.
faces_eyereads or searches
“How squarely a surface faces the eye: facing 1 square on, 0 edge on, below 0 turned away.”
2 inputs
- pointstring or array“a name (a bone such as hand_l, a fingertip such as index_tip_l, a rig point such as port) or [x, y, z] in the frame”
- normalarray or null“the surface's normal, gun frame; a rig normal by the point's name if left out”
visiblereads or searches
“The share of a small disc round a point that the eye sees with nothing (arms, rifle) in the way.”
2 inputs
- pointstring or array“a name (a bone such as hand_l, a fingertip such as index_tip_l, a rig point such as port) or [x, y, z] in the frame”
- radius_cmnumber
screenon 10 other serversreads or searches
“Where a point falls on a 90 degree, 16:9 screen from the eye: x and y from -1 to 1, and whether it is on screen.”
1 input, 1 required
- pointstring or arrayrequired“a name (a bone such as hand_l, a fingertip such as index_tip_l, a rig point such as port) or [x, y, z] in the frame”
solveon 6 other serversruns code or commandsdescribed as changing data
“Searches rifle moves from the current pose for one meeting every goal, and leaves the scene there.”
6 inputs, 2 required
- dofsobjectrequired“roll, swing, pitch, right, forward, up -> [min, max]”
- goalsarrayrequired“each {type: faces_eye|visible (point, min), on_screen (point), clearance (parts, ignore, max_cm), anatomy (side, fingers), grip (side, back_max_cm, palm_max_cm…”
- keep_handsarray“hands that keep their hold on the rifle as it moves (arm IK)”
- pivotstring
- samplesinteger
- maximizeinteger or null“a goal's index to push higher once all are met”
record_clipcreates or changes datadescribed as changing data
“Builds a clip from poses you set: start (a name), key (the current pose at a time in seconds), stop (bakes the frames, each bone eased from key to key).”
5 inputs, 1 required
- actionstringrequired
- clipstring or null
- secondsnumber
- fpsnumber
- easeboolean
load_clipcreates or changes datadescribed as changing data
“Adds a clip from a file: .pose.json bone data, an FBX animation, or a BVH (for example a text-to-motion model's output).”
3 inputs, 2 required
- clipstringrequired
- pathstringrequired
- bone_mapobject or null“the file's bone names -> this rig's”
scan_clipreads or searches
“Plays a clip frame by frame and runs each check.”
2 inputs, 2 required
- clipstringrequired
- checksarrayrequired“each {type, ...}: clearance (parts, ignore, max_cm), anatomy (side both|l|r, fingers: the rules broken, counted), grip (side, back_max_cm, palm_max_cm: the han…”
fix_clipcreates or changes datadescribed as changing data
“Mends a clip against the checks and stores a new clip (out, default <clip>_fixed): pops are blended again from the good frames round them; a hold puts the hand back on its grip; a contact moves the w…”
5 inputs, 2 required
- clipstringrequired
- checksarrayrequired“each {type, ...}: clearance (parts, ignore, max_cm), anatomy (side both|l|r, fingers: the rules broken, counted), grip (side, back_max_cm, palm_max_cm: the han…”
- outstring or null
- max_swing_degnumber
- spread_framesinteger
view_coverreads or searches
“The share of the player's view the arms cover (all, its lower left third, its bottom middle third): the arms rendered alone from the eye as a mask.”
Takes no inputs.
solve_gripruns code or commandsdescribed as changing data
“Searches a hand's hold on the rifle: the palm on mark (moved along the barrel), the elbow toward each pole.”
10 inputs, 2 required
- sidestringrequired
- markstring or arrayrequired“a name (a bone such as hand_l, a fingertip such as index_tip_l, a rig point such as port) or [x, y, z] in the frame”
- alongarray“[from_cm, to_cm] along the barrel from the mark”
- stepsinteger
- polesarray or null“elbow poles, arms frame cm; the idle elbow and four round it if left out”
- view_budgetobject or null“{lower_left, bottom_middle}: the most of each third the arms may cover”
- clearance_max_cmnumber
- ignorearray
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”
- rollsarray“the hand's roll about the barrel to try, degrees”
retarget_clipdescribed as changing data
“Plays another rig's clip on this rig with one hand held on this gun's own hold (its rest hold, or mark) by arm IK, fingers mended: shared motion, the gun's own grip.”
10 inputs, 2 required
- clipstringrequired
- sidestringrequired
- markstring or array or null
- outstring or null
- framestring“gun: the gun bone, cm (+X gun's left, +Y barrel, +Z up); arms: the arms' space, cm; view: from the eye, cm (+X right, +Y forward, +Z up)”
- keep_from_snumber or null
- keep_to_snumber or null
- holdstring“the rig's idle hold, or the hold it stands in now (after solve_grip)”
- gun_moveobject or null“move_gun's arguments applied to every frame first (the other hand keeps its hold): a rifle carried lower or closer”
- polestring or array or null“where the elbow points (arms frame, cm), as solve_grip's best gives it”
shift_handdescribed as changing data
“Moves one hand frame by frame by the given deltas (gun frame, cm): a hand that holds a part whose track changed follows the part's new path.”
4 inputs, 3 required
- clipstringrequired
- sidestringrequired
- deltasarrayrequired“[[seconds, [x, y, z]], ...]: the hand's move in the gun frame (cm), straight lines between”
- outstring or null
check_setreads or searches
“Every check on a clip in one summary for a gate: the worst clearance and when, the frames that break an arm or finger rule, the frames a hand in hold_sides is not holding, and each frame's numbers.”
5 inputs, 1 required
- clipstringrequired
- ignorearray
- clearance_max_cmnumber
- hold_sidesarray
- sidesstring
save_clipon 1 other servercreates or changes datadescribed as changing data
“Writes a clip to the output folder's clips/: pose.json bone data, and fbx for a game engine.”
3 inputs, 1 required
- clipstringrequired
- formatsarray
- root_namestring or null“the armature's name in the FBX (Unreal reads it as the root bone)”
renderon 22 other serversgenerates contentdescribed as changing data
“Renders the pose as one labelled contact sheet: eye is the player's camera (90 degrees, 5 cm near plane); right, left, top and front look at the rifle from outside.”
1 input
- viewsarray

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 31 tools
Says what it returns: 64% of 28 tools
States limits, defaults or errors: 0% of 29 tools
Says when to use it: 0% of 28 tools
Items covered per tool: 1.7 of 4 on average

Counted from the listing

Parameters with a description: 36% of 103
Tools with a description: 100% of 31
Typical description length: 275 characters

The tool set

Counted from the listing

Tools: 31
Size of the list: about 6,473 tokens for an agent to load (characters ÷ 4)
Naming: 19 of 31 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 31 of 31 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the PyPI package poselab-mcp

Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).

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": {
    "poselab-mcp": {
      "command": "uvx",
      "args": [
        "poselab-mcp==0.7.0"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "poselab-mcp": {
      "command": "uvx",
      "args": [
        "poselab-mcp==0.7.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "poselab-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "poselab-mcp==0.7.0"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"poselab-mcp","type":"stdio","command":"uvx","args":["poselab-mcp==0.7.0"]}'

Claude Code

claude mcp add --transport stdio poselab-mcp -- uvx poselab-mcp==0.7.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- uvx poselab-mcp==0.7.0

Optional settings the entry also lists (left out above): POSELAB_BLENDER, POSELAB_RIGS, POSELAB_OUT.
This runs the publisher's code on your machine (uvx). 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). 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.7.0
Latest stable: 0.7.0
Status: current
Withdrawn: no

Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha256-2e632160a3293a580…
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 0 in the last month

Source: pypistats.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.7.0 on PyPI	Exists and can be installed	matches	PyPI · 2026-10-23
Repository github.com/hpdkhoa/poselab-mcp	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

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

Namespace: io.github.hpdkhoa · 6 servers
GitHub owner: a personal account (hpdkhoa)

Repository: github.com/hpdkhoa/poselab-mcp
Stars: 1
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-10-23; security policy read from GitHub · 2026-10-23.

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

7 of 8 record checks met · 1 does not apply

#14,745 of 15,112 packages by monthly downloads, tied with 367 others
Not ranked by stars: 1 star (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.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. 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. How each check works · Leaderboards

Common questions about io.github.hpdkhoa/poselab-mcp

Answered from the data above

Is io.github.hpdkhoa/poselab-mcp safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 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 listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 16 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.hpdkhoa/poselab-mcp been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.hpdkhoa/poselab-mcp do?

It lists 31 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, run code or commands and generate content. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.hpdkhoa/poselab-mcp change or delete data?

16 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.hpdkhoa/poselab-mcp publish a security policy?

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

Is the listed version current?

Yes. The registry lists 0.7.0, the latest stable release on PyPI.

Where is the source code of io.github.hpdkhoa/poselab-mcp?

In github.com/hpdkhoa/poselab-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.

Similar servers

Same topic · AI-read

io.github.leancoderkavy/premiere-proMCP for Adobe Premiere Proalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.KyaniteLabs/kinocutKinocutalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.KyaniteLabs/mcp-videomcp-videoalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
tech.kyanitelabs/kinocutKinocutalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.ODU33104/rive-mcpalso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one
io.github.kimimgo/viznoirviznoiralso has tools that creates or changes data, runs code or commands, generates content, reads or searchescompare with this one

Active servers whose topic is also “media-and-design” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

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

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
2,156 msConnected after 0 redirects.
Read the inventory: 31 tools, 0 resources, 0 prompts.
2,680 msFinished: 2 checks exercised.

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

media-and-design

AI-classified · 2026-10-23

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

Python

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

prompts, resources, tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

pypi

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sha256)

package registry · 2026-10-23

Signature / provenance

does not apply

PyPI publishes no registry signature or attestation equivalent to npm dist.signatures

Dependency advisories

none known

OSV.dev · 2026-10-23

Popularity

0 downloads a month

package registry · 2026-10-23

Publisher signals

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“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. “io.github.hpdkhoa/poselab-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.hpdkhoa/poselab-mcp

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](https://protocolprobe.com/api/v1/badge/io.github.hpdkhoa/poselab-mcp)](https://protocolprobe.com/mcp/servers/io.github.hpdkhoa/poselab-mcp)

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.

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