Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Server helper for get_property_list with a per-list token verifier, plus a compliance check

Open
#577 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
api, backend, testing

Research direction

Start by reading the existing PropertyListChangedWebhook and webhook.Publisher.Emit integration, then inspect the conformance work in #351 to find its entry point. Implement the server registration pattern alongside those helpers, including verifier and page-loader injection. Done means get_property_list accepts a valid per-list token, rejects invalid tokens, loads pages, and passes a compliance test that issues and resolves a reference.

Written by the indexing model from the issue text.

Description

Problem

A Go buyer platform that hands out PropertyListReferences has to serve them itself. The SDK has no get_property_list handler and no way to plug in a per-list token check. The reference's auth_token is meant to open that one list, in place of the platform's normal auth. There's also no compliance check that a buyer's references can be resolved.

The webhook side is in better shape: PropertyListChangedWebhook is generated, and webhook.Publisher.Emit handles delivery with retries.

Ask

  1. A server helper that registers get_property_list, with a pluggable per-list token verifier and page loader.
  2. A compliance test: issue a reference, resolve it with the helper from the companion issue, and page through it. This may fit the conformance work in #351.

Same request in the TypeScript SDK: adcontextprotocol/adcp-client#3330.

Dominant language
Go
Stars
4
Forks
2
Avg merge
17h
Merged PRs (30d)
21

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from adcontextprotocol/adcp-go

All issues in adcontextprotocol/adcp-go

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.