Skip to content

MCP servers › io.github.ddgod123 › rentpro

MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19

rentpro MCP server

Registry name io.github.ddgod123/rentpro

RentPro Beijing Premium Rental Consultant — the publisher's title

by ddgod123 · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Beijing premium rental consultant: demand intake, published listings, viewing handoff. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-19version 0.19.19Pythonstreamable HTTP16 tools

Summary

io.github.ddgod123/rentpro is a remote MCP server listed in the official MCP registry at version 0.19.19, under the namespace of the GitHub account ddgod123. Its linked repository, github.com/ddgod123/MCP-Rent-Skill, belongs to the same GitHub account. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 16 tools, 0 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do 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)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • 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
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
16
Last tested
2026-11-19

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-19 (mcp.smartrent.xin), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.19.19).

Add to your client

Observed fact

This server accepted a session without any credential and lists 3 tools whose name or declaration suggests they change data (request_viewing, update_rental_demand, update_rental_demand_filters). That is our reading of the names; we did not call them. Source: our connection, 2026-11-19.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-19
Mode
read-only (no tool calls)
Latest version
0.19.19, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
First listed version
2026-11-15 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-11-15 to 2026-11-19; 2 in the 90 days before the 2026-11-19 snapshot.
Most recent 2 versions
  • 0.19.19 · 2026-11-19
  • 0.19.18 · 2026-11-15
(versions still listed in the registry only)
Registry data
snapshot 2026-11-19
Package and repository
checked 2026-11-19
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

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. Does not apply: listed version cannot be installed or is withdrawn. 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

Version 0.19.18 (published 2026-11-15) → 0.19.19 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.

The publisher published no GitHub release note for version 0.19.19: the repository has no release tagged for it.

Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.

What it is

What does this server offer?

Observed inventory
16tools
0resources
0prompts

None of its 16 tools are described as changing anything. For 16 the reading was uncertain, so no mark is shown.

  • check_rentpro_skill_update

    “仅在用户主动选择菜单 9(检查更新)时调用的只读版本检查工具。传入已加载 SKILL.md 的 version,比较当前 MCP 服务声明的最新 Skill 版本;发现更新时返回可复制的宿主安装地址和更新指引。不下载、不修改本地文件;不要把工具原始结果直接展示给租客。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input
    • current_skill_versionstring“宿主当前加载的 SKILL.md version,例如 0.9.0;无法读取时可不传”
  • confirm_rental_demand

    “确认租房需求版本。推荐只传 session_token;如传 demand_id,必须同时传同一需求的 session_token。仅允许确认满足当前字段目录必填规则的版本,默认物业类型、租金预算、地段位置、居室;以 search_ready 为准。”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • demand_idnumber“需求 ID”
    • mutation_idstring“本次确认幂等键;宿主重试同一次写入时必须复用”
    • session_tokenstring“匿名会话令牌”
    • version_nonumber“要确认的版本号,可选;不传则确认当前版本”
  • get_listing_detailon 2 other servers

    “获取一套当前可展示挂牌的客户可读详情。默认返回完整详情;通过 include 按需返回 core、price、photos、notes、property、semantic、transport 或 surrounding。只能使用 search_listings/search_listings_by_demand 返回的真实 listing_id/listing_ref 调用;不要向客户展示 li…”

    Publisher declares: read-only yes · destructive no · idempotent no · open-world yes

    2 inputs, 1 required
    • includearray“按需返回:core、price、photos、notes、property、semantic、transport、surrounding;不传则返回完整详情”
    • listing_idnumberrequired“房源 ID,必填”
  • get_manager_contact

    “获取房源经理公开联系方式和填写入口。保存并沿用返回的 session_token;pending 表示尚未写库。仅在主动询问联系方式时调用;明确要求联系、核验或约看使用 request_viewing。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • session_tokenstring“沿用当前对话凭证以关联需求和客资;首次省略。”
    • source_agentstring“已知客户端标识,如 dsh、workbuddy、codex;未知省略,不向客户展示。”
    • source_channelstring“真实宿主渠道,如 dsh、workbuddy;未知传 mcp,不猜测、不向客户展示。连接头优先;可选兼容旧客户端。”
  • get_property_filter_catalog

    “读取当前可用于楼盘层级筛选的条件目录。当前严格支持:小区有泳池、小区有健身房、小区有会所、标准层高、交付日期/近 N 年内、小区有地暖、明确环线区域/沿线,以及存在五居及以上、300㎡及以上、一梯一户的真实户型;户型条件是存在型匹配,不代表整盘全部户型或当前在租。新增商场、超市/生鲜(不含菜市场)、地铁站的明确直线距离条件;附近/方便等模糊要求先澄清距离范围。环线只接受目录列出的明确区域/沿线值…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    Takes no inputs.

  • get_rental_demand

    “读取当前租房需求、search_ready、缺失必填项及 demand_editor 授权编辑链接。网页保存后必须用原 session_token 读取最新需求,齐全再自动调用 search_listings_by_demand,未齐继续收集。也可为原需求刷新过期链接,不创建另一份需求。如传 demand_id,必须同时传同一需求的 session_token。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • demand_idnumber“需求 ID”
    • session_tokenstring“匿名会话令牌”
  • get_rental_filter_catalog

    “读取当前基础需求字段目录 basic_catalog、必填项 required_fields、深度筛选目录和已保存条件。推荐只传 session_token;如传 demand_id,必须同时传同一需求的 session_token。字段名称与允许提交的编码以目录为准;record_only 只记录需求,不承诺用于严格筛选。目录不返回数据库来源字段。”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    3 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • demand_idnumber“需求 ID”
    • session_tokenstring“匿名会话令牌”
  • list_release_properties

    “菜单 2、业务楼盘目录。区→商圈→楼盘逐级浏览。无参返回行政区总览overview;选区/商圈后为properties,每页最多10个楼盘。原样展示display_text,保留换行。仅明确下一页续查。不修改需求,无需session_token,不受 search_ready 门禁限制。不返回具体房源;仅本页有房楼盘创建浏览会话。listing_count=0表示发布范围内暂无可展示房源,不承诺…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs
    • business_districtstring“所选商圈名称,包含匹配;可结合district,无匹配不放宽”
    • cursorstring“仅明确下一页沿原view、区/商圈传上次pagination.next_cursor;每轮一页,不自动翻完”
    • districtstring“所选区名或编码,如朝阳、110105;不修改需求”
    • viewstring“overview区域总览;properties楼盘分页。有区/商圈默认properties,否则overview;明确看全部用properties”
  • render_rental_demand_template

    “查看当前需求,不自动搜索。无已填条件返回 template_mode=blank_intake 和完整空白 template,无 demand_editor,不补定制页提示、链接或按钮。有实际条件(含部分填写、不限、否定或网页筛选)返回 template_mode=saved_demand 和有效 demand_editor,在内容外单独展示编辑入口。按内容判断。推荐只传 session_tok…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • demand_idnumber“需求 ID”
    • session_tokenstring“匿名会话令牌”
    • version_nonumber“需求版本号,可选”
  • request_viewingon 5 other servers

    “提交客户咨询/看房意向到 RentPro 后台。适用于用户愿意留联系方式、希望顾问联系、需要人工核验或对一套/多套房源明确感兴趣时;该工具只创建或补全客资包,不自动承诺预约成功。支持匿名 session_token 续接同一会话;传 demand_id 时必须同时传同一需求的 session_token,服务端会校验归属后再把当前需求版本和快照附到客资。宿主重试同一次提交时复用 mutation…”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    22 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • contact_namestring“联系人姓名或称呼”
    • contact_typestring“联系方式类型:phone 或 wechat”
    • contact_valuestring“手机号或微信号”
    • conversation_idstring“宿主当前对话 ID,用于把本次客资与原始对话关联”
    • demand_idnumber“当前租房需求清单 ID。传入后自动把当前需求版本和快照附到客资,供房源经理人工核验”
    • host_conversation_idstring“真实宿主聊天 ID;未知省略。”
    • host_instance_idstring“已知宿主实例/租户范围。”
    • interested_listingsarray“感兴趣房源 ID 列表,可包含多个”
    • lead_idnumber“已有客资 ID。若之前已创建待补充联系方式客资,再次提交时传入该 ID 进行续填”
    • listing_idnumber“主房源 ID,可选”
    • mutation_idstring“本次写入幂等键;宿主重试同一次提交时必须复用同一值”
    • notestring“客户备注,例如预算、其他需求”
    • preferred_timestring“期望看房时间,例如:明天下午3点”
    • requirementsobject“结构化需求快照,例如预算、区域、居室、面积和通勤条件”
    • session_tokenstring“匿名会话令牌。用于同一宿主会话续接匿名咨询;传 demand_id 时必填且必须属于同一需求;未传 demand_id 时可自动生成”
    • sourcestring“兼容来源字符串,例如 mcp、mcp:workbuddy、mcp:workbuddy:it_seed_user:pilot_2026_09。默认 mcp”
    • source_agentstring“具体 Agent 或客户端标识,例如 workbuddy、codex、self_agent”
    • source_campaignstring“活动或试点批次,例如 beijing_luxury_pilot_2026_09”
    • source_channelstring“自报宿主或获客渠道,例如 dsh、cursor、workbuddy、it_seed_user;未知不猜。连接头优先于参数,仅用于分析,不用于权限或结算”
    • source_toolstring“触发客资的工具或入口,默认 request_viewing”
    • summarystring“对话需求摘要,例如预算、区域、通勤、硬性要求和已关注房源”
  • search_listingson 231 other servers

    “查询北京可展示挂牌,按楼盘分页:每页一个楼盘的全部匹配房源;明确单楼盘直查一次返回全部。用户明确回复“下一个楼盘”才沿原条件、排序和session_token传pagination.next_cursor。直查传精确property_name(名称/别名/英文名),不匹配地址标题;无需模板、不受search_ready、不修改已有需求。歧义先澄清。原样展示display_text;total、d…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    30 inputs
    • bedroomsnumber“居室数量,例如 2”
    • citystring“城市,枚举:beijing(当前有数据)、shanghai/guangzhou/shenzhen(预留)。默认 beijing”
    • commute_targetstring“通勤目标:guomao、wangjing、zhongguancun、jinrongjie”
    • consultation_idstring“沿用系统咨询 ID。”
    • cursorstring“仅用户明确回复“下一个楼盘”时传上次pagination.next_cursor;沿用原筛选、排序和session_token,一次返回下一楼盘全部挂牌,不自动翻页”
    • districtstring“行政区划代码,例如 110105(朝阳)、110108(海淀)”
    • excludearray“用户明确不考虑的硬排除项,例如 [别墅, 服务式公寓, 合租]”
    • featuresarray“受控特征标签,全部满足,例如 [bathtub, floor_heating, pet_friendly]”
    • has_clubhouseboolean“是否有会所;用于筛选有会所或无会所的楼盘”
    • has_elevatorboolean“是否有电梯;用于筛选确认有电梯或确认无电梯的楼盘,待确认项不命中”
    • has_gymboolean“是否有健身房;用于筛选确认有健身房或确认无健身房的楼盘,待确认项不命中”
    • has_poolboolean“是否有泳池;用于筛选确认有泳池或确认无泳池的楼盘,待确认项不命中”
    • host_conversation_idstring“真实宿主聊天 ID;未知省略。”
    • host_instance_idstring“已知宿主实例/租户范围。”
    • keywordstring“楼盘、区域或地址关键词,例如:望京、太阳宫、中建宸园”
    • max_areanumber“最大建筑面积,平方米”
    • max_commute_minutesnumber“到 commute_target 的最大楼盘通勤分钟数”
    • max_floor_heightnumber“楼盘层高上限,米”
    • max_pricenumber“最高月租,元”
    • min_areanumber“最小建筑面积,平方米”
    • min_floor_heightnumber“楼盘层高下限,米”
    • min_pricenumber“最低月租,元”
    • pet_allowedboolean“是否明确允许养宠物;空值不命中”
    • property_namestring“具体楼盘直查:单个完整楼盘名称、别名或英文名,例如:东直门8号;仅匹配楼盘,不匹配房源标题或地址。无需需求模板,不要拼入多个楼盘;通常不同时传 keyword”
    • property_typestring“物业类型:住宅、别墅、行政公寓;也接受 1/2/3”

    and 5 more not listed here.

  • search_listings_by_demand

    “按同一持久化需求搜索,结果每页一个楼盘并完整返回该楼盘的匹配挂牌,不按套数截断。仅用户明确回复“下一个楼盘”才沿原需求版本、排序和身份传next_cursor。推荐只传session_token;demand_id须带同需求令牌,未齐不搜索。原样展示display_text:有效期→同版本demand_summary→全量统计→本页楼盘资料、demand_editor→本楼盘全部挂牌。摘要保留s…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    6 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • cursorstring“仅用户明确回复“下一个楼盘”时传本次pagination.next_cursor;沿用session_token、需求版本和排序,一次返回下一楼盘全部挂牌;条件变化后重查,不自动翻页”
    • demand_idnumber“需求 ID”
    • session_tokenstring“匿名会话令牌”
    • sortstring“排序:match、newest、price_asc、price_desc。默认 match”
    • version_nonumber“需求版本号,可选”
Show 4 more tools
  • search_release_properties

    “按楼盘条件筛选当前 MCP 发布范围中的业务楼盘,而不是挂牌房源。filters 每项含 filter_code、operator、value;多个条件默认 AND。支持泳池、健身房、会所、地暖(eq,布尔值)、标准层高(gt/gte/lt/lte/eq,单位米)、交付日期(日期比较使用 YYYY-MM-DD;within_years 使用整数年数)、明确环线区域/沿线(property_rin…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • filtersarrayrequired“楼盘条件数组;每项含 filter_code、operator、value。多个条件默认全部满足(AND)。先读取 get_property_filter_catalog,不要自行猜字段编码。”
  • start_rental_demand

    “用户独立选择菜单数字1后启动咨询,或已启动后明确重领空表时调用。每次返回 template_mode=blank_intake,只发 intake_template,不附定制页提示/链接/按钮,该响应不返回 demand_editor;重复和重试同样适用。已有需求再选1用 render_rental_demand_template。本工具只创建或续接原草稿,不清空、不搜索、不带入启动前输入。”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world yes

    8 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • host_conversation_idstring“真实宿主聊天 ID;未知省略。”
    • host_instance_idstring“已知宿主实例/租户范围。”
    • mutation_idstring“本次启动幂等键;宿主重试同一次写入时必须复用”
    • session_tokenstring“匿名会话令牌;同一宿主会话后续继续使用,首次可不提供”
    • source_agentstring“已知客户端。”
    • source_campaignstring“已知活动批次。”
    • source_channelstring“已知宿主渠道。”
  • update_rental_demand

    “按字段级 patch 更新当前租房需求并生成新版本。推荐只传 session_token;如传 demand_id,必须同时传同一需求的 session_token。先读取 basic_catalog,仅提交允许自然语言录入的字段,未知字段会拒绝。可先保存草稿,以返回的 search_ready 和缺失字段为准;默认必填为物业类型、租金预算、地段位置、居室。null 或 clear_fields…”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    8 inputs
    • confirmboolean“是否将新版本同时设为已确认版本”
    • consultation_idstring“沿用系统咨询 ID。”
    • demand_idnumber“需求 ID”
    • input_textstring“用户原始修改说明,可选”
    • mutation_idstring“本次更新幂等键;宿主重试同一次写入时必须复用”
    • patchobject“字段级补丁,例如 location/budget/bedrooms/area/must_have/preferred/exclude/pending/weights/clear_fields”
    • session_tokenstring“匿名会话令牌”
    • statusstring“状态:active、paused、archived”
  • update_rental_demand_filters

    “直接保存租房需求的深度筛选条件并生成新版本。推荐只传 session_token;如传 demand_id,必须同时传同一需求的 session_token。用户可以通过网页填写,也可以由宿主把明确表达转换成受控 filter_code 后调用。filters 是整组替换;先读取当前条件并合并未删除项。可传 version_no 和 filter_catalog_revision 做并发校验。”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    8 inputs
    • consultation_idstring“沿用系统咨询 ID。”
    • demand_idnumber“需求 ID”
    • filter_catalog_revisionstring“读取目录时的深度筛选目录 revision,可选;传入后服务端做并发校验”
    • filtersarray“筛选条件数组;每项含 filter_code、requirement_level、operator、value、weight”
    • input_textstring“用户原始筛选表达,可选”
    • mutation_idstring“本次深筛保存幂等键;宿主重试同一次写入时必须复用”
    • session_tokenstring“匿名会话令牌”
    • version_nonumber“读取目录时的当前需求版本号,可选;传入后服务端做并发校验”

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. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. 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-11-19.

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

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 109
Tools with a description
100% of 16
Typical description length
252 characters

The tool set

Counted from the listing

Tools
16
Size of the list
about 4,289 tokens for an agent to load (characters ÷ 4)
Naming
16 of 16 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 16 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 remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-19 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.smartrent.xin/public-mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "rentpro": {
      "url": "https://mcp.smartrent.xin/public-mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "rentpro": {
      "type": "http",
      "url": "https://mcp.smartrent.xin/public-mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"rentpro","type":"http","url":"https://mcp.smartrent.xin/public-mcp"}'
Claude Code
claude mcp add --transport http rentpro https://mcp.smartrent.xin/public-mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "rentpro": {
      "type": "streamableHttp",
      "url": "https://mcp.smartrent.xin/public-mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "rentpro": {
      "httpUrl": "https://mcp.smartrent.xin/public-mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.rentpro]
url = "https://mcp.smartrent.xin/public-mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "rentpro": {
      "url": "https://mcp.smartrent.xin/public-mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.smartrent.xin/public-mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • 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.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. 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-19. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.

Own host

  • security.txt. No security.txt at https://mcp.smartrent.xin/.well-known/ (HTTP 404, 2026-11-19). No security.txt at https://smartrent.xin/.well-known/ (HTTP 404, 2026-11-19). Source: mcp.smartrent.xin/.well-known/security.txt · read 2026-11-19.
  • A2A agent card. No A2A agent card at https://mcp.smartrent.xin/.well-known/ (HTTP 404, 2026-11-19). No A2A agent card at https://smartrent.xin/.well-known/ (HTTP 404, 2026-11-19). Source: mcp.smartrent.xin/.well-known/agent-card.json · read 2026-11-19.

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
Remote endpoint mcp.smartrent.xin/public-mcpSession openedmatchesour test · 2026-11-19
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-19
Repository github.com/ddgod123/MCP-Rent-SkillOpens publiclymatchesapi.github.com · 2026-11-19

Who made it?

Feature #7 · lineage

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

Namespace
io.github.ddgod123
GitHub owner
a personal account (ddgod123)
Repository
github.com/ddgod123/MCP-Rent-Skill
Stars
0
Repository age
31–90 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-19; security policy read from GitHub · 2026-11-16.

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.

Tool list changes

Our reads compared · no tool called

Hosted endpoint mcp.smartrent.xin/public-mcp

No change in the tool list across 2 reads (2026-11-16 to 2026-11-19; versions 0.19.18 to 0.19.19).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-19 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • 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
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-16). 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 io.github.ddgod123/rentpro

Answered from the data above

Who publishes io.github.ddgod123/rentpro?

The registry ties the namespace io.github.ddgod123 to the GitHub account ddgod123; only its owner can publish under it. Its linked repository, github.com/ddgod123/MCP-Rent-Skill, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.ddgod123/rentpro safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 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. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.ddgod123/rentpro need an API key or sign-in?

It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.ddgod123/rentpro been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Does io.github.ddgod123/rentpro 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 io.github.ddgod123/rentpro?

In github.com/ddgod123/MCP-Rent-Skill, 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

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

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-19
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants 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
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks 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-data
    Checks 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-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks 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-hiding
    Checks 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
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-19, 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.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,324 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 16 tools, 0 resources, 0 prompts.
  4. 8,529 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
pending: added at the next monthly refresh
listed 2026-11-19; 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-19
Hosting type
registry · 2026-11-19
MCP capability
tools
our test · 2026-11-19
Transport
streamable HTTP
registry · 2026-11-19
Required credentials
none declared
registry · 2026-11-19 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-19
Lifecycle status
registry · 2026-11-19
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 31–90 days · stars: 0–9
api.github.com · 2026-11-19
Maintenance
api.github.com · 2026-11-19
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-19

“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.ddgod123/rentpro: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.ddgod123/rentpro

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: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.ddgod123/rentpro)](https://protocolprobe.com/mcp/servers/io.github.ddgod123/rentpro)

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